Delivery-Date: Sat, 11 Oct 2014 19:24:21 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD 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 9EDBF1E0D3D;
	Sat, 11 Oct 2014 19:24:19 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7C98431346;
	Sat, 11 Oct 2014 23:24:15 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7DC4D312DA
 for <tor-talk@lists.torproject.org>; Sat, 11 Oct 2014 23:24:11 +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 OfaF9uOucNv3 for <tor-talk@lists.torproject.org>;
 Sat, 11 Oct 2014 23:24:11 +0000 (UTC)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com
 [209.85.220.169])
 (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 59A7F3124E
 for <tor-talk@lists.torproject.org>; Sat, 11 Oct 2014 23:24:11 +0000 (UTC)
Received: by mail-vc0-f169.google.com with SMTP id hy4so4356581vcb.28
 for <tor-talk@lists.torproject.org>; Sat, 11 Oct 2014 16:24:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:content-type;
 bh=/wlurPYm1VzKcPe8aqLoRrnybZqfGoztb9PG7+YOnGk=;
 b=Y+SKqaiO9oXOcXtVpmHi52KIh2MpIYTEQTalqGnsejxG15yQrgnZ4o5Yrybc51SIh5
 xu5DK7J+hS7PWelM+sdCXbVbcnCH928BWN+wfh8+ESaI0SzqRJnje8LfpEHr5BWcDofL
 530JsOyXfqafzRl/0yen92mlGl0P8NYQBw5L054CYb485DWKkA1b4Y+PvRECiNCjl+Dh
 O++ZpFZk0Fwmngz8ZOOIU2QTygTc33i5Mxlmc8p3i/klyPBG2WCy1iDzi4ZTEMMUn0ll
 VHJFNCvoOv6+nohnO141zGMVi2BJVwrsBuqgueM9USX6Q4XQo7h0iVWFh9vFIQYiSXe1
 /vIw==
X-Gm-Message-State: ALoCoQljgF8484sGxjE7ymEjdNtJJRoQJEKNla5y4Pq0xmFxeEJ8pR5RLEiXtX9BPVZ9HizECrh8
MIME-Version: 1.0
X-Received: by 10.220.193.67 with SMTP id dt3mr13048591vcb.4.1413069848825;
 Sat, 11 Oct 2014 16:24:08 -0700 (PDT)
Received: by 10.220.40.2 with HTTP; Sat, 11 Oct 2014 16:24:08 -0700 (PDT)
In-Reply-To: <CANLPe+NLOokeocoYk6nPY2Tdzs+GMPYZQDNtiyyqFPhiTWpvng@mail.gmail.com>
References: <CANLPe+M-MqKbxC3Jah5OggRa7j-7jU-KJ0tZJ0Z1mS8r0aPgNg@mail.gmail.com>
 <597899488.3907271413062124086.JavaMail.root@ip-10-181-20-37.ec2.internal>
 <719492467.3957621413068678816.JavaMail.root@ip-10-181-20-37.ec2.internal>
 <20141011231732.GE54413@moria.seul.org>
 <CANLPe+NLOokeocoYk6nPY2Tdzs+GMPYZQDNtiyyqFPhiTWpvng@mail.gmail.com>
Date: Sun, 12 Oct 2014 08:24:08 +0900
Message-ID: <CANLPe+O8o5iLmC-7uUh3kM1+JUaw=RKOh8A5iWzzrKGSyZsy1A@mail.gmail.com>
From: Casey Rodarmor <casey@rodarmor.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Tor Relay Smartphone App
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>

Also, might there be a way for nodes to advertise their speed? Assuming
that there is no incentive to lie about being slow, it might be a useful
heuristic so that a node with any bandwidth can join and benefit the
network.

On Sun, Oct 12, 2014 at 8:22 AM, Casey Rodarmor <casey@rodarmor.com> wrote:

> What is the minimum bandwidth/latency that a node requires in order for it
> to benefit the network? I read here* that 100 kilobytes/s each way would be
> enough, which I imagine many phones are capable of handling, and represent
> a small fraction of a wifi network's bandwidth.
>
> *https://www.torproject.org/docs/tor-doc-relay.html.en
>
> On Sun, Oct 12, 2014 at 8:17 AM, Roger Dingledine <arma@mit.edu> wrote:
>
>> On Sun, Oct 12, 2014 at 12:04:37AM +0100, 4dcb8ec3@opayq.com wrote:
>> > Hi, yes it's called Orbot see here
>> >
>> >
>> https://play.google.com/store/apps/details?id=org.torproject.android&hl=en_GB&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dorbot&pcampaignid=APPU_Hbc5VJLDFMjB7AaK9oBw
>> >
>> > And here's a Reddit thread on setting it up as a non exit node
>> >
>> >
>> http://www.reddit.com/r/Bitcoin/comments/2im3cz/turn_your_android_into_a_tor_relay_get_bitcoin/
>>
>> Unfortunately, your smartphone likely doesn't have the cpu to push much
>> traffic, and also your home wifi or equivalent very likely doesn't have
>> the bandwidth to be a good relay.
>>
>> So this is a really appealing idea in theory, but in practice such relays
>> are much much less useful than faster relays -- to the point that slow
>> relays actually hurt the network because they produce bad performance
>> for users who are unlucky enough to pick them.
>>
>> It would be cool to live in a world where things were different --
>> perhaps one day somebody will do the rest of the research and
>> engineering work involved in making the Conflux design work:
>> http://freehaven.net/anonbib/#pets13-splitting
>> But we took a step in the direction away from Conflux when we moved
>> from three guard nodes per user to one.
>>
>> --Roger
>>
>> --
>> 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
>>
>
>
-- 
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

