Delivery-Date: Sun, 27 Jul 2014 02:41:52 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 50CE71E0A44
	for <archiver@seul.org>; Sun, 27 Jul 2014 02:41:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 127862E4AB;
	Sun, 27 Jul 2014 06:41:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AC5AD2B7CE
 for <tor-talk@lists.torproject.org>; Sun, 27 Jul 2014 06:39:42 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id oxcH7g6uXjRL for <tor-talk@lists.torproject.org>;
 Sun, 27 Jul 2014 06:39:42 +0000 (UTC)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com
 [IPv6:2607:f8b0:400c:c03::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 8BD302B6B7
 for <tor-talk@lists.torproject.org>; Sun, 27 Jul 2014 06:39:42 +0000 (UTC)
Received: by mail-vc0-f176.google.com with SMTP id id10so9467795vcb.21
 for <tor-talk@lists.torproject.org>; Sat, 26 Jul 2014 23:39:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=zOZU8x90FrvybaG5EJfhgj58vx+VXpny/p1aiT2o/18=;
 b=kqEWObpyzE1qNJMCU/F8QII20+dj7LHx/LCYSzYjpVrv7VHwlA5i1Z+rJ8m4kybNfj
 Oqq131gP0OWgEfUjttU1Ro0qeBcgkVMQwTQtihXaBlJk7zqhGSn0/YZsxoeRUk2c6Kso
 dx+ZX6U2TvLr4lTXJpfFpuk2lYGIKmt3QFG5NLdy1p/86UWkGMHu02zENRC2kcGMYEo9
 VkKu93QWcPq+yfV5viYELVFlFJcKe61vUsha5+LyZHnkcSy+/kDG8uuR1h8eFPabfvSJ
 kOB0I0SK3FV/eXpG/QTdAxEo4mKiJ+3r9rEuaLrRhj5Ew7THZbhrKNusCostSnf48XqL
 Rmgw==
MIME-Version: 1.0
X-Received: by 10.53.13.200 with SMTP id fa8mr4631673vdd.57.1406443180213;
 Sat, 26 Jul 2014 23:39:40 -0700 (PDT)
Received: by 10.221.65.131 with HTTP; Sat, 26 Jul 2014 23:39:40 -0700 (PDT)
In-Reply-To: <CADop2NG0vpz6rJqu8=YWdxz1NdNn+5z8ruoH8d=wL6LnVPy3kg@mail.gmail.com>
References: <CADop2NG0vpz6rJqu8=YWdxz1NdNn+5z8ruoH8d=wL6LnVPy3kg@mail.gmail.com>
Date: Sun, 27 Jul 2014 02:39:40 -0400
Message-ID: <CAD2Ti2_+uknyEO3j12iVC3EwR5688aZTzUcP7OMpm6oMiABPbQ@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] What are use cases made unpleasant by Tor's speed?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

> * Hidden Services
> Wiki and TorChan come to mind.

These have always worked perfectly fine.

> * Streaming video/porn -- I can imagine people in many jurisdictions

Low bandwidth video from a good codec is not intolerable, and
reinforces good old fashioned content is more important than
needless pixels. And porn? Wtf, really?!

Tor itself isn't slow, it's the bandwidth the nodes provision
that makes it seem slow in the face of many users trying
to watch porn (really?), presentations (wasted) in hidef,
and leech attacks.
And they all seem to think they can abuse/leech 7x their
usage to the net for free... that's unsustainable and uncool.

In the long term steady state, users must support with open
bandwidth, and the circs may need to path through available
bandwidth.


Now if latency (keystrokes) were to get much worse, that
would seem less tolerable than lower bandwidth.
And Tor doesn't support UDP for things like Mosh, so
you're stuck with TCP's issues there.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

