Delivery-Date: Fri, 11 Jul 2014 18:12:01 -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 CD2DF1E0B60
	for <archiver@seul.org>; Fri, 11 Jul 2014 18:11:59 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 44F7830517;
	Fri, 11 Jul 2014 22:11:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2CFD63050B
 for <tor-talk@lists.torproject.org>; Fri, 11 Jul 2014 22:06:09 +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 bukPSIcAgy4H for <tor-talk@lists.torproject.org>;
 Fri, 11 Jul 2014 22:06:09 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id D2B4530508
 for <tor-talk@lists.torproject.org>; Fri, 11 Jul 2014 22:06:08 +0000 (UTC)
Received: from [10.1.0.2] ([37.24.146.242]) by mail.gmx.com (mrgmx103) with
 ESMTPSA (Nemesis) id 0LxPgU-1WUx1T2dII-016ubz for
 <tor-talk@lists.torproject.org>; Sat, 12 Jul 2014 00:06:05 +0200
Message-ID: <53C05FCC.9060708@unterderbruecke.de>
Date: Sat, 12 Jul 2014 00:06:04 +0200
From: Random Tor Node Operator <tor@unterderbruecke.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAP3fC8Q548JhJtP880WKkqc-raWMw8+Qxhn0KVGSdiMZFyQefQ@mail.gmail.com>
In-Reply-To: <CAP3fC8Q548JhJtP880WKkqc-raWMw8+Qxhn0KVGSdiMZFyQefQ@mail.gmail.com>
X-Enigmail-Version: 1.5.2
X-Provags-ID: V03:K0:9MThJ/MrlbNnxpLN6byk/ldAgVJ0qlTkXoQqu6FNzF4w6yEfnYK
 7mMu8jdEcR81gvQo2TFidfhCjGGBFqfo+py7mfnGRdI4/y3ES2+pHDMfRGTZKOwcR5KJy8v
 hV/hZgBg+HRfp+F/JXg2kWNT9Pg+xNIHYslZuy9lLneB9e+IV6c9XI18s2USQcJJLBPV+VT
 mjPfULJJlfnpugDMxtb8g==
Subject: Re: [tor-talk] Putting the "Tor" back in Torrent
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/11/2014 11:12 PM, Helder Ribeiro wrote:
> 4. Make the Popcorn Time fork also **be a relay by default*
> whenever possible**.
> 
> Nobody would agree to do this on the main tor software for a
> thousand reasons, but it's an *app* and you can decide to do that
> in it independently. If you're going to add a lot of load to the
> network, you have to give back.


There are at least 2 problems with many "make users a relay by
default" ideas:

1. Some overzealous website administrators blacklist all Tor relay
IPs, even non-exits. [1]
This might cause lots of frustration in users when they realize that
some sites lock them out because they used to be running a Tor relay
for some time on their IP. Right now, that type of problem is limited
to very few cases where relay IPs are used for non-Tor purposes as well.

2. Currently, the time constant of the Tor system to pick up a new
relay[2] is way bigger than the time of a typical Bittorrent session
(This is a handwaving guesstimate of mine).
So the effect of contributing to Tor that way would in most cases be
minimal.
One could think of a way to have Tor use something like "short-lived
relays", which are perhaps propagated through a DHT instead of the
regular consensus system. On the one hand, that would make "giving
something back to the network" a whole lot easier. On the other hand,
I can hardly estimate what the security and anonymity implications of
that would look like.




[1]
https://lists.torproject.org/pipermail/tor-relays/2013-August/002531.html

[2] https://blog.torproject.org/blog/lifecycle-of-a-new-relay
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTwF/EAAoJEJe61A/xrcOQW5kP/jFB8l+/GrjDjb1gwJfRu3GY
LfBWv0LUpRRV6NjqB7y9IZI6kyPSJtB9Vb8DJ91QYt653SX4Rwa0POCgDGVfQRmn
HN9GWPCz9yr5jI8NU9HaFIYu+DZhYtnvlNjDDG4/ltyUr78k5uh5syrdaxwLJuV+
fue1Ef+QcybR+atkGCiMHJnn8rJcpmnFL/ntAhozGXTf6jMlAMKrekeGKc/bcNMb
t8yRk0slKqlkL1/okPk7rO7tlEvGRPet8YQP6GrswT5EGk0BryxDHIwth2fJDvSK
dYtI1l1XndMlVtZXOlIS2FXiack6X75aGaaot4oPQF+vUuj4AaUbC9qb6+z5FCQ8
y6hIjJNoJZ2b4m5SN3TWj/hdWAkLOVT6XUckd1Ddt03krQJH6Zs1B0IEa9wT52jm
zlrxwOcUGRyvTC6R1Jh18Gj7SJE5U0E3S+sODFJIbCAcmGkwc5ZQ3j1muvJ2JvfL
h53q8ZQvgzP5TnqcebUEtxKjJQtWO20+2gFDghz1+Fw+nZDDeHNVyHjEIFpPnxyy
OEUYRzGY+iRWa6Wnvq+6jsts8z+zpn6cgd9PkQf+xQOkbZliG6W1RMzLlIElDYKe
bGfO3VQZJHM6+gutt0JJPd7RTgJ5LGhi+utKNzZw2p7RjT6+jU62BVPJQ22sXGBT
Co5y+99/dnsVR61hqy30
=l95K
-----END PGP SIGNATURE-----
-- 
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

