Delivery-Date: Fri, 12 Sep 2014 23:02:39 -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 0EC9B1E0B14;
	Fri, 12 Sep 2014 23:02:37 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6B092307F2;
	Sat, 13 Sep 2014 03:02:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 76E6E2E93D
 for <tor-talk@lists.torproject.org>; Sat, 13 Sep 2014 03:02:30 +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 GnZ0u7HEDGdC for <tor-talk@lists.torproject.org>;
 Sat, 13 Sep 2014 03:02:30 +0000 (UTC)
X-Greylist: delayed 362 seconds by postgrey-1.34 at eugeni;
 Sat, 13 Sep 2014 03:02:30 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 5D73C2C35F
 for <tor-talk@lists.torproject.org>; Sat, 13 Sep 2014 03:02:30 +0000 (UTC)
Received: from mail.ncf.ca (localhost [127.0.0.1])
 by mail.ncf.ca (Postfix) with ESMTP id 43D5B9F660
 for <tor-talk@lists.torproject.org>; Fri, 12 Sep 2014 22:56:25 -0400 (EDT)
Received: from [192.168.2.3] (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: fq743)
 by mail.ncf.ca (Postfix) with ESMTPSA id 1A3FA9F5C4
 for <tor-talk@lists.torproject.org>; Fri, 12 Sep 2014 22:56:25 -0400 (EDT)
Message-ID: <5413B240.5000705@ncf.ca>
Date: Fri, 12 Sep 2014 22:56:00 -0400
From: stn <stn@ncf.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.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>
In-Reply-To: <CAJVRA1TrTZHbdopJs8GS94oE04=6si=5Anx=94aMGGXYBYr_NQ@mail.gmail.com>
X-NCF-Filtered: By ProxSMTP on pallando Fri Sep 12 22:56:25 2014 -0400 (EDT)
Subject: [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>

hi,
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 home isp etc.

i did so because i have yet to build a good box for my home connection 
to service a torbridge for residential broadband

(suggestions as to what to use welcome.  pcbsd, debian or ubuntu flavour 
etc.  i'm using older h/w likely dual core 2.3ghz.  i think i have 4 gig 
ram but willing to invest in more.)

i can see the value keeping torcloud alive even if users stick with it 
for only a year of low cost donation.

no one knows me so i cannot handle sensitive procedures but i'm willing 
to help take other work off someone's hands that doesn't involve the 
required trust level.  eg update documentation and field help once i 
know process a bit better.

in a support message lunar mentioned torcloud needs a maintainer. 
perhaps having a helper might make it easier for someone to apply their 
name to it?

since tor requires consistent uptime i can see torcloud being an asset.  
as much as i'll try to get a solid nix box going at home i suspect 
torcloud node might be more reliable vs people like me building boxes 
and running nix fulltime at home to service tor. (?)

steve







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

