Delivery-Date: Fri, 17 Apr 2015 21:33:48 -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 BBDBC1E0C83
	for <archiver@seul.org>; Fri, 17 Apr 2015 21:33:46 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C2F153426E;
	Sat, 18 Apr 2015 01:33:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E6B3633A3C
 for <tor-talk@lists.torproject.org>; Sat, 18 Apr 2015 01:33:36 +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 BncTiOn2pDPi for <tor-talk@lists.torproject.org>;
 Sat, 18 Apr 2015 01:33:36 +0000 (UTC)
Received: from spam.esheavyindustries.com (spam.esheavyindustries.com
 [104.131.11.202])
 (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 CC57433842
 for <tor-talk@lists.torproject.org>; Sat, 18 Apr 2015 01:33:36 +0000 (UTC)
Received: by spam.esheavyindustries.com (Postfix, from userid 33)
 id 6AE2240114; Fri, 17 Apr 2015 21:33:33 -0400 (EDT)
To: tor-talk@lists.torproject.org
X-PHP-Originating-Script: 0:rcmail.php
MIME-Version: 1.0
Date: Fri, 17 Apr 2015 19:33:33 -0600
From: social@sponsor-privacy.com
In-Reply-To: <7384AAFFF17.00000386beatthebastards@inbox.com>
References: <710b761efa7d892ff39b9a6394b5b2a3@sponsor-privacy.com>
 <553160a6.4010508@openmailbox.org> <55317340.6040806@openmailbox.org>
 <f460c93e6746d29c1161746bd25d4b12@sponsor-privacy.com>
 <b5e8df4dfdc51443220a5cda4a3c9902@sponsor-privacy.com>
 <7384AAFFF17.00000386beatthebastards@inbox.com>
Message-ID: <773cbc28b33638d3babba4a51e222a89@sponsor-privacy.com>
X-Sender: social@sponsor-privacy.com
User-Agent: Roundcube Webmail/0.9.5
Subject: Re: [tor-talk] New site attempting to help Tor grow
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>

On 2015-04-17 17:14, I wrote:
> 1 TB a month for $60usd a year?
> I have several 5 TB a month for $12usd a year.
> Are there reasons I don't know of that makes the higher rate necessary?
> 
> Robert

I went with DigitalOcean because their API is what allows the 
provisioning process to be automated which means less time spent by 
humans setting things up. The only way this was going to work for me is 
if the basic ordering process was 100% automated with me only tending to 
the one-offs or odd failures. DigitalOcean charges $5 per month for 
their base VPS (https://www.digitalocean.com/pricing/) which is where 
the $60 a year comes from.
Using a VPS provider that requires a manual order each time as well as 
manual setup of the Tor client (even if using something like salt or 
ansible you still need to run a command) just didn't make sense for a 
side project.

I appreciate all of the feedback but it seems as if this project doesn't 
make sense yet so I'll probably shut it down and put it on the self 
until a better solution can be determined (if at all).
-- 
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

