Delivery-Date: Sat, 13 Sep 2014 21:03:00 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 95FC41E0A78;
	Sat, 13 Sep 2014 21:02:58 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3357C2641D;
	Sun, 14 Sep 2014 01:02:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 689672536F
 for <tor-talk@lists.torproject.org>; Sun, 14 Sep 2014 01:02:50 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 0BcUM9nHZwLS for <tor-talk@lists.torproject.org>;
 Sun, 14 Sep 2014 01:02:50 +0000 (UTC)
Received: from mail.ncf.ca (mail.ncf.ca [206.47.12.45])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 4804622841
 for <tor-talk@lists.torproject.org>; Sun, 14 Sep 2014 01:02:50 +0000 (UTC)
Received: from mail.ncf.ca (localhost [127.0.0.1])
 by mail.ncf.ca (Postfix) with ESMTP id 533EE9F19B
 for <tor-talk@lists.torproject.org>; Sat, 13 Sep 2014 21:02:48 -0400 (EDT)
Received: from [192.168.2.5] (d24-156-234-120.home4.cgocable.net
 [24.156.234.120])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested) (Authenticated sender: fr223)
 by mail.ncf.ca (Postfix) with ESMTPSA id 280BD9F19A
 for <tor-talk@lists.torproject.org>; Sat, 13 Sep 2014 21:02:48 -0400 (EDT)
Message-ID: <5414E936.1090306@ncf.ca>
Date: Sat, 13 Sep 2014 21:02:46 -0400
From: stn <stn@ncf.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.0;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20140911101248.4C48C290C1@scatolo>
 <54134ECB.2080301@infosecurity.ch>
 <CAJVRA1TrTZHbdopJs8GS94oE04=6si=5Anx=94aMGGXYBYr_NQ@mail.gmail.com>
 <5413B240.5000705@ncf.ca>
In-Reply-To: <5413B240.5000705@ncf.ca>
X-NCF-Filtered: By ProxSMTP on pallando Sat Sep 13 21:02:48 2014 -0400 (EDT)
Subject: Re: [tor-talk] keeping torcloud alive
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 neglected to mention that i'm willing to sign legal docs/promises to 
abide by torproject wishes when helping out torcloud if it can be 
maintained.

hoping someone with proper trust level can help maintain.  as i 
mentioned i'm willing to help to take duties of the primary maintainers 
plate as is required and suitable.

i'm repeating myself a little but
i really think torcloud has potential to be very good for the tor 
network if costs can be managed.

i keep thinking about network reliability.  we had several outages this 
summer in the province of ontario.  bell canada's backbones affected 
smaller ISPs including mine.  while running a bridge at home is good i 
doubt it will be as reliable as my torcloud bridge judging by outages 
this summer.

this might continue sadly as canada cannot keep up with traffic 
requiring exchanges right now.  we route traffic to the US quite often 
even if the domains are .ca to .ca.  we're short on infrastructure.  
makes little sense since IX hardware is relatively cheap.

cheers
steve

[...]
> new talk subscriber. i'm
> volunteering to help keep torcloud alive by offering help even though 
> i can't be primary maintainer.
>
> i recently got a torcloud  node up and running. $3 month first year is 
> quite good. stable and once going no hassles.  i like the idea. less 
> prone to outages than my h
-- 
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

