Delivery-Date: Sun, 28 Feb 2016 12:02:07 -0500
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,UNPARSEABLE_RELAY
	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 401A51E030A;
	Sun, 28 Feb 2016 12:02:05 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C857D3A022;
	Sun, 28 Feb 2016 17:02:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AA2A83A020
 for <tor-talk@lists.torproject.org>; Sun, 28 Feb 2016 17:01:58 +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 OltZwEeIvS8i for <tor-talk@lists.torproject.org>;
 Sun, 28 Feb 2016 17:01:58 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 894AA3A011
 for <tor-talk@lists.torproject.org>; Sun, 28 Feb 2016 17:01:58 +0000 (UTC)
Received: from cotinga.riseup.net (unknown [10.0.1.164])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id EF3791A1E48
 for <tor-talk@lists.torproject.org>; Sun, 28 Feb 2016 17:01:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1456678916; bh=17sZvE0RzxkENdlf9TyR7NVUvd/hjCgI8i8bbfsShXU=;
 h=From:Subject:Date:References:In-Reply-To:To:From;
 b=f3TDga59RFeAf3PYOAVxCM+JJVQrFBS/CfKWmEYMOpNJYhJKfFye5GJuna8t+Ba76
 4s9Z50wLyCIfrKFG8IKrZSapQICQX4Vb+sHdue9EQUkdLt3v3ry3V5Bx1TjNydy3O7
 bOWV7o3uB4XEXyx8sg6KaCUaHIgEPd+h0kG2j08Q=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: scfith) with ESMTPSA id BF8F44002B
From: Scfith Rise up <scfith@riseup.net>
Mime-Version: 1.0 (1.0)
Message-Id: <5134ABF1-A5A6-45AB-8103-2E85001564D4@riseup.net>
Date: Sun, 28 Feb 2016 12:01:54 -0500
References: <A154C659-98B9-4B5A-AE8B-89A67EA8BF78@riseup.net>
 <56C63981.2080604@gmail.com> <56C63AD3.4000002@justaguy.pw>
 <CAD2Ti2-Znf2kCogg_grDqCeWR4FwHERAE1giZgLggoM-6CUFkA@mail.gmail.com>
In-Reply-To: <CAD2Ti2-Znf2kCogg_grDqCeWR4FwHERAE1giZgLggoM-6CUFkA@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
Subject: Re: [tor-talk] large increase in .onion domains
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>

Now the spike is up to over 80000 domains. The Tor Project has had more than a few days now to analyze this, any update or feedback regarding what these appear to be beyond "we need to wait and see." Personally, I think it is, in fact, Ricochet. 

> On Feb 21, 2016, at 4:09 PM, grarpamp <grarpamp@gmail.com> wrote:
> 
>> On Sat, Feb 20, 2016 at 06:18:12AM -0700, Mirimir wrote:
>> Or maybe Harry71 isn't detecting them. I recall that grarpamp was
>> finding onion sites. Maybe he'll comment.
> 
> His seems to be down at the moment, oniondb, monitor and a
> few others are up... just spidering on the back, index middle, search
> on the front. I typically had more with custom tools, but it was work,
> and with over 9000 onions, doing other things now, maybe later.
> Nice to see new guys fielding stuff.
> 
> The other area are hsdir researchers, they're traditionally quiet...
> But that game is long public and has many players now so maybe
> someone will comment on the surge from their data there.
> 
> The usual explanations all seem plausible.
> And onionland's big enough to have them all now.
> 
> Onionland awaits you... :)
> 
> [And I2P and ... too]
> -- 
> 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
-- 
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

