Delivery-Date: Sat, 21 Mar 2015 01:52:50 -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.1 required=5.0 tests=BAYES_00,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 1631B1E0B52
	for <archiver@seul.org>; Sat, 21 Mar 2015 01:52:45 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A916D348DF;
	Sat, 21 Mar 2015 05:42:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 57C1334679
 for <tor-talk@lists.torproject.org>; Sat, 21 Mar 2015 05:42:46 +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 Y6XJZ_SmORzZ for <tor-talk@lists.torproject.org>;
 Sat, 21 Mar 2015 05:42:46 +0000 (UTC)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com
 [IPv6:2607:f8b0:4001:c05::230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 355DD32F72
 for <tor-talk@lists.torproject.org>; Sat, 21 Mar 2015 05:42:41 +0000 (UTC)
Received: by igbqf9 with SMTP id qf9so4321691igb.1
 for <tor-talk@lists.torproject.org>; Fri, 20 Mar 2015 22:42:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virgil.gr; s=dkim;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=hM7naq3ucdXFjrT69XZRWF5peumHTn5RVcNLBwBpMfk=;
 b=bBF7G9IAXxh0gEiFIET3Sl5b3kx1y14dSk6nbbZN8lm7w2d4ce+hUqwjGlvnlTUI96
 wy/katI0fzTBOLQ2C7QpIb9idi5TOtzqX9D4K5OX/dsH64WQNSCR7HC7sVoDD2fAbIr2
 mP0vBPMJFNSdCxcshGd+twtnPWUvIFOauCK+0=
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=hM7naq3ucdXFjrT69XZRWF5peumHTn5RVcNLBwBpMfk=;
 b=RtOVRtUAHHZn52SOqIyB0zThOxBmpEMsOTNM+UUNb3MrnAMmv7AXmFPU+hH/crSZJZ
 72YKNPfKc+zyfLujlyvffkkv1MlwatG9bCBDPq2uTpg7PibGDPsDXs4+D6aHLpJdClU3
 Rnxz8LIXDDVfwh6Yye7sH4lwN+Q1brI0F7aX2GQccdMlwzSpUfdEZkwk5wkh2cSj2u+M
 yp9Gyc6cKcvuMdwZ9+0bIqB6CKWjjWBX/tZVML/J9K+52Sch95yVGDtVjhHE4bgLkgaL
 IxVUtzSJR0GBPWRQP5vExrPr1cQRTDO517tzY6F9lP4E1lkc5KX3uuLbQKt4i+Wt0E2p
 uucA==
X-Gm-Message-State: ALoCoQlUvQJ4LQved1Bj3DJ5QChttElWsZl8NYG4sBTjjKezKd1BEuYQmF1HaWnschly93Hpiedm
MIME-Version: 1.0
X-Received: by 10.50.9.97 with SMTP id y1mr1502254iga.34.1426916559256; Fri,
 20 Mar 2015 22:42:39 -0700 (PDT)
Received: by 10.50.111.43 with HTTP; Fri, 20 Mar 2015 22:42:39 -0700 (PDT)
In-Reply-To: <550C9A31.30203@openmailbox.org>
References: <550C9A31.30203@openmailbox.org>
Date: Sat, 21 Mar 2015 13:42:39 +0800
Message-ID: <CADop2NESynFwcn_Z0+riGuUVw2QCmZiMPUK=+sbQYpgjVvTvhg@mail.gmail.com>
From: Virgil Griffith <i@virgil.gr>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [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>

"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."

for what it's worth this website has been started.  I'll post a beta to
tor-talk when it's presentable.  I remain very optimistic about the "impact
per unit effort" for such a gamification site.

-V


On Saturday, March 21, 2015, Nusenu <nusenu@openmailbox.org> wrote:

> -----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 <javascript:;>
> 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

