Delivery-Date: Thu, 04 Sep 2014 18:36:35 -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_SIGNED,
	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 A2C3E1E0E23;
	Thu,  4 Sep 2014 18:36:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5BDD52612E;
	Thu,  4 Sep 2014 22:36:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 205662566F
 for <tor-talk@lists.torproject.org>; Thu,  4 Sep 2014 22:36:26 +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 8Yy_mzNVnIPI for <tor-talk@lists.torproject.org>;
 Thu,  4 Sep 2014 22:36:26 +0000 (UTC)
Received: from mail.headstrong.de (mail.headstrong.de [81.7.4.112])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id E235924FED
 for <tor-talk@lists.torproject.org>; Thu,  4 Sep 2014 22:36:25 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by mail.headstrong.de (Postfix) with ESMTP id B4CE51C01C7E
 for <tor-talk@lists.torproject.org>; Fri,  5 Sep 2014 00:36:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=headstrong.de;
 h=content-transfer-encoding:content-type:content-type
 :in-reply-to:references:subject:subject:mime-version:from:from
 :date:date:message-id:received; s=mail; t=1409870176; x=
 1411684577; bh=EKOX5f9Mn7Eun6HWofcES8LFIspnGGfHDmSheAEOrms=; b=X
 4ioB9hkqRrBgaomzvitNEpaGvZPSdqQ/hoYlcyt6qgKRjFd0dBIuT76VP94Yu3k6
 2Vqeg1peUt4/vu+b+bZuzBdt11xPad9SvxplQTo9k9EkjtTnUB2ghaXCv66DWEwU
 RhkobKPYTRyjY30bB4umOTv6ilb5v36Xmg+OEAgdCc=
X-Virus-Scanned: Debian amavisd-new at mail.headstrong.de
Received: from mail.headstrong.de ([127.0.0.1])
 by localhost (mail.headstrong.de [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id aFiGZ5yU7zns for <tor-talk@lists.torproject.org>;
 Fri,  5 Sep 2014 00:36:16 +0200 (CEST)
Message-ID: <5408E9AA.9050506@torservers.net>
Date: Fri, 05 Sep 2014 00:37:30 +0200
From: Moritz Bartl <moritz@torservers.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CADop2NGjDi3x-hKxRC7wBAWu5cYWzkHe+hg703UuxkPiSC2X=A@mail.gmail.com>
 <5408D678.7070305@torservers.net>
 <CADop2NH=G+FNJ8H+B-ok79EhfPVCPRUxB6BbrZwj8-8KXQB2Ng@mail.gmail.com>
In-Reply-To: <CADop2NH=G+FNJ8H+B-ok79EhfPVCPRUxB6BbrZwj8-8KXQB2Ng@mail.gmail.com>
Subject: Re: [tor-talk] Tentative results of analysis of data on
	metrics.torproject.org
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>

On 09/05/2014 12:08 AM, Virgil Griffith wrote:
> If that ascent is due to you, this screams to the success of the
> torservers.net model.  It might be useful to see that plot without
> Torservers.net in there.  If I figure out how to make sense of the raw
> consensus file I may plot it.

Essential to the torservers.net idea is to teach others to run relays
and share expertise. I put up a "How to get from a Debian base install
to a 'complete' Tor exit relay" since the beginning. Most of our partner
orgs are actively involved in local outreach and serve as points of
contacts for other relay operators. We receive roughly one mail every
second week to support@ from someone who asks us for help in setting up
their own relays. Also, obviously, having more orgs run around telling
people "You have to run relays!" is helpful. :) Over time, we handed out
a couple of thousand "Run a Tor relay" posters.

Long story short, even if you filtered out the actual relays run by all
our partners, it not necessarily reflects "this is what would have
happened without them".

While we're at "how to grow the network": One idea that has been around
for long time is to provide abuse handling services and legal protection
("Put our data into your WHOIS and we will take care of 99% of the
trouble; also, for the remaining 1%, we will pay a lawyer and help you
find one."). This is possible, and I believe it would be very helpful in
growing exit relays, but I personally can't take it on at the moment.

I would still be quite interested in a (pie?) chart that shows
guard/middle/exit capacity per family, ideally over time. I haven't seen
any "per family" analysis.

-- 
Moritz Bartl
https://www.torservers.net/
-- 
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

