Delivery-Date: Mon, 13 Jul 2015 19:47:38 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 D84E31E0E02;
	Mon, 13 Jul 2015 19:47:35 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 703FA37836;
	Mon, 13 Jul 2015 23:47:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6AD213783F
 for <tor-talk@lists.torproject.org>; Mon, 13 Jul 2015 23:47:28 +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 mdWSJvGiOcax for <tor-talk@lists.torproject.org>;
 Mon, 13 Jul 2015 23:47:28 +0000 (UTC)
Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238])
 (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 349213783E
 for <tor-talk@lists.torproject.org>; Mon, 13 Jul 2015 23:47:25 +0000 (UTC)
Mime-Version: 1.0
Date: Mon, 13 Jul 2015 23:47:18 +0000
From: bstduot@ruggedinbox.com
To: tor-talk@lists.torproject.org
Message-ID: <9665a3c714da200c1e03fa81cbce1ec5@ruggedinbox.com>
X-Sender: bstduot@ruggedinbox.com
Subject: Re: [tor-talk] OnionBalance Hidden Service has over 1 million
 successful hits in just 3 days
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

I was the operator of the following user-agents on 5 different virtual 
servers:

- i am helping\\!
- i am also helping\\!
- i am also in on this.
- me too\\!
- late to the party but here i am\\!


I have very rudimentary stats (request start, curl exit code, request 
stop) as I didn't spend much time setting these up. Each server was 
configured to restart tor every X minutes in hopes of setting up new 
circuits.

Requests ended shortly before this email.

- i am helping\\! X=10; exit status 0 = 1142748
- i am also helping\\! X=15; exit status 0 = 1176423
- i am also in on this. X=16; exit status 0 = 1258477
- me too\\! X=20; exit status 0 = 1267831
- late to the party but here i am\\! X=10; exit status 0 = 786205

I wish I could have done more but it's something at least.



About the lack of 'In-Reply-To': new email account.

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

