Delivery-Date: Tue, 19 May 2015 01:59:33 -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 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 4DA2E1E0CF9
	for <archiver@seul.org>; Tue, 19 May 2015 01:59:31 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 76B2335502;
	Tue, 19 May 2015 05:59:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D75BF354FA
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 05:59:23 +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 era0i42EwCvJ for <tor-talk@lists.torproject.org>;
 Tue, 19 May 2015 05:59:23 +0000 (UTC)
Received: from mail.headstrong.de (mail.headstrong.de
 [IPv6:2a02:180:a:25:2::1])
 (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 AC267354F5
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 05:59:23 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by mail.headstrong.de (Postfix) with ESMTP id 67B591C003CD
 for <tor-talk@lists.torproject.org>; Tue, 19 May 2015 07:59:19 +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=1432015159; x=
 1433829560; bh=++3EK4414gUDIxY8aPoQdm7WjUTp9SUafbja0ePSs/s=; b=B
 zegcjc5u5qptBBu97wRSj0iOa2od0QaYrg0kZjnjoeKXRMNDQ/H4iIT0bBqQhpJT
 V1kjkmdQzEa46ihI4xDuaVJm/9QxkFXKIcROGvjMTYpPbh3fusYK4jKd/0HuhThn
 8kILx4G13EkXPGolXQDAWIOh+M9pabWpYyPtxjyAS8=
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 F5Pl2hxdRiHP for <tor-talk@lists.torproject.org>;
 Tue, 19 May 2015 07:59:19 +0200 (CEST)
Message-ID: <555AD136.3060906@torservers.net>
Date: Tue, 19 May 2015 07:59:18 +0200
From: Moritz Bartl <moritz@torservers.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAD2Ti29Meq-7X0B4pBd3MK00s7ASkOizavu1c9XoTg6Qs-42MQ@mail.gmail.com>
In-Reply-To: <CAD2Ti29Meq-7X0B4pBd3MK00s7ASkOizavu1c9XoTg6Qs-42MQ@mail.gmail.com>
Subject: Re: [tor-talk] Relays - exits, placement, analysis, OS, etc
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 05/19/2015 07:25 AM, grarpamp wrote:
> Nusenu and a few others have been working on
> various analysis of relays...
> - finding historical and current drops into the network
> - current location maps
> - geographics, network, and OS where relays are needed for diversity
> - developing families from suspect metadata
> - ISP good/bad
> - badexit flags documented
> - etc
>
> These projects seem important enough to consider giving
> them a home at TPO or ensuring there's at least an index
> page on the wiki referencing them all.

We're currently discussing a redesign of torservers.net. I've always
imagined it to be(come) a home for Tor relay operators, not only one
group or a particular set of operators. I'm more than happy to provide
that space and connect interested folks to the volunteer web designer
who offered his help. After all, it sounds like a good fit :-)

We mostly live on OFTC in #torservers and #zwiebelfreunde (German).

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

