Delivery-Date: Fri, 20 Mar 2015 18:08:20 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,URIBL_BLOCKED
	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 04B371E0AD9
	for <archiver@seul.org>; Fri, 20 Mar 2015 18:08:19 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 41EF334808;
	Fri, 20 Mar 2015 22:08:15 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3DD12347F7
 for <tor-talk@lists.torproject.org>; Fri, 20 Mar 2015 22:08:11 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 wwoGBI0tSYJK for <tor-talk@lists.torproject.org>;
 Fri, 20 Mar 2015 22:08:11 +0000 (UTC)
Received: from mail.openmailbox.org (mail.openmailbox.org [62.4.1.34])
 (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 EEAB92D82F
 for <tor-talk@lists.torproject.org>; Fri, 20 Mar 2015 22:08:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail.openmailbox.org (Postfix) with ESMTP id 5E0BE2E057A
 for <tor-talk@lists.torproject.org>; Fri, 20 Mar 2015 23:08:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openmailbox.org;
 h=content-transfer-encoding:content-type:content-type:subject
 :subject:mime-version:from:from:date:date:message-id:received;
 s=openmailbox; t=1426889283; bh=FQdkOrh2ZntCW83Cdxp8kbKIpm9Rmv2
 q81d+da/b9UU=; b=JXpv9n3JT+XUKHeAmrkdpzRwDY5P/4kngv7swiGd/C34k32
 u2ZkItV4sKxlX8z1g7NWueiqJad4kK7faRpcLiT+82AjwNj2XkbVmiuRpqqsyPYp
 /RWK6uMxvVIJQ3VXg3gBwrgiZ60s5RL1WuPT1U5F9TXrn1CXAQWyoJwnFiHY=
X-Virus-Scanned: amavisd-new at openmailbox.org
Received: from mail.openmailbox.org ([62.4.1.34])
 by localhost (mail.openmailbox.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id tCEqLVGf0PGM for <tor-talk@lists.torproject.org>;
 Fri, 20 Mar 2015 23:08:03 +0100 (CET)
Message-ID: <550C9A31.30203@openmailbox.org>
Date: Fri, 20 Mar 2015 22:07:45 +0000
From: Nusenu <nusenu@openmailbox.org>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
Subject: [tor-talk] Who runs the Tor Network? An Overview using MyFamily Data
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: SHA512

Hi,

currently we use globe [1] compass [2] or old school torstatus [3] to
get an overview of what relays are around and who might operate them.

None of these 'tools' provide an easy way to aggregate relay data to
have a look at the bigger picture (Who runs most of the tor network?).

I generated* a preliminary overview based on MyFamily data, that
should provide an overview of the big tor relay operators:

https://github.com/nusenu/misc-files/blob/master/biggest_tor_relay_operators_by_MyFamily.txt
(Only the top 15 have names next to them because that was a manual task ;)

In the future that table might just be another compass checkbox saying
"Group by MyFamily" (or a static page generated once an hour).

Note: If you compare this with other overviews that uses contactInfo
to aggregate relays
https://github.com/nusenu/misc-files/blob/master/tor-relays_by_contact.txt
you will notice some big operators are missing. That means that they
are not using MyFamily (properly).
Also because MyFamily is a cumbersome setting for relay operators
there might be misconfigurations** that result in multiple
(overlapping) families.

Positive side effect: By using MyFamily to aggregate relays, I hope to
creating incentives for relay operators to actually configure MyFamily
on their relays. MyFamily avoids using multiple relays - operated by a
single entity - in a single tor client circuit.

Also, relay ops running many "smaller" relays hopefully will become
more visible (and receive more acknowledgments for their
contributions) [4].

If you are a relay operator yourself, you can easily check if you
configured your relays properly by entering any of your relay
fingerprints on https://compass.torproject.org (family field). If the
search result does not show all your relays then there is something
wrong with your MyFamily configuration.

regards,
Nusenu


[1] https://globe.torproject.org/#/top10
[2]
https://compass.torproject.org/#?exit_filter=all_relays&links&sort=cw&sort_reverse&country=
[3] http://torstatus.blutmagie.de/

[4]
https://lists.torproject.org/pipermail/tor-relays/2015-February/006436.html
Moritz wrote:
"We still lack the "gamification" Relay Challenge website that Virgil
was talking about. It would just sum up all relays of a family, and
then it really does not matter any more."


*) basically compass -f in a loop has been used to generate that overview.
I also required at least two members in a Family - which is a bad idea
because you will "loose" single big relays like IPredator - this will
be changed.

**) This should become less of a problem for relay ops with tools like
ansible
https://github.com/nusenu/ansible-relayor
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVDJowAAoJEFv7XvVCELh0obkP/jHJOQdB0KozozObL/j9sJes
PezMiV31fONjWt/gEOEe9Gq3HnHW8kAam+ZxEkeGplLv03dYy7ri02EV0T4Rhu2b
fxOEQRJKOxOkQbZEU88CThJ4jWBBVxSNxY/OYWaZU8EKz4ofghmd0jWD0kVrFBO+
cp3w//87LGyLkbcrVgSbeHL7DEACpVuIDZf2Ye5k6lFZF7V1NdpJF5RKGGVnmJLj
/uylRv4j0eBWdg2FBfTBaQL73N7qWe8bTeG7gAfhfJiQZTX9E9ow4uFbCqlQu5tO
KZNG3mfdRMMUFy5Rlhapp0KX3dX0UpIyZ7O2Cg8y6E2gjKCuZVG8Vw+yiBU3XLf+
yN+YE5VlnOBddlvKf6NVIEjPca5KrSgGUjmi+i+eDwEv4QD3/ghjJmxPijtQDahy
p0s3EyZodnSVNO6JleXJj7MEFK1bib+zlExYWdRuW4V4RD+5g8R1eqaM1RPUc8WH
XPJuFA43EFvWhrYsYu4+1rvlgFJGnB+dUkFai0x4RKt/CmJomOVJK/1ohpHuqafM
vRp2hOVXVEn2irhKpl4NtuCvmo3GBx5g9+GC+yjIZAX7bykYuyuBoake6rMuqllX
z91uCDYn1rk3ugHVSXzLBOcjU89oH9LLhLos2I+O2QbWMLR1/tFWgzHkfRTvLyNc
MME9LEePbOdQq5c6GAV9
=c+oy
-----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

