Delivery-Date: Fri, 17 Apr 2015 11:43:15 -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 9A5E41E0ACE
	for <archiver@seul.org>; Fri, 17 Apr 2015 11:43:13 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9A3D320AE1;
	Fri, 17 Apr 2015 15:43:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9F32234280
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 15:43:04 +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 cI7q2tERNWx8 for <tor-talk@lists.torproject.org>;
 Fri, 17 Apr 2015 15:43:04 +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 85BFC20982
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 15:43:04 +0000 (UTC)
Received: by spam.esheavyindustries.com (Postfix, from userid 33)
 id 14C7940114; Fri, 17 Apr 2015 11:43:01 -0400 (EDT)
To: tor-talk@lists.torproject.org
X-PHP-Originating-Script: 0:rcmail.php
MIME-Version: 1.0
Date: Fri, 17 Apr 2015 09:43:01 -0600
From: social@sponsor-privacy.com
In-Reply-To: <CAM8M=kim==me1X5etJ=vSn8fuXGNiCLgMYg3x4KYxzRNN-xyXw@mail.gmail.com>
References: <710b761efa7d892ff39b9a6394b5b2a3@sponsor-privacy.com>
 <55311E91.2050108@torservers.net>
 <CAM8M=kim==me1X5etJ=vSn8fuXGNiCLgMYg3x4KYxzRNN-xyXw@mail.gmail.com>
Message-ID: <8d516ae733489c9368dad8f9b0bb5180@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>

Gareth, appreciate the feedback, here are some responses to your 
questions:


On 2015-04-17 09:19, Gareth Llewellyn wrote:
> We're working on doing something similar at BrassHornCommunications.uk 
> with
> a 'Bridges on Demand' offering which'll spin up a new private bridge 
> *(tick
> box config for choosing meek plugins etc)* and provisions with Chef /
> Ansible.
> 
> *Questions:*
> Will you be open sourcing any of your automation tools?
> 

I have thought about this as it might allow others to spin up a similar 
site. The issue right now is a lot of the
account specific parameters are hard-coded so I need to work on pulling 
those out before making it something other
groups could use. Being an OSS fan though the idea is to at some point 
make the code public. The truth is though
that all we're really doing is calling various APIs from other vendors, 
chaining them together and wrapping it in
some logic. I wish it was a lot cooler than that but the app itself is 
pretty plain.


> Will all your relays be within the same AS / DC or spread about?
> 

As of today they are placed randomly between two different DCs from a 
single provider. On the "TODO" list though is
to expand that so that we're using multiple providers and multiple DCs.


> Are you using OpenVZ / KVM et al / dedicated servers or 3rd party VPS
> services e.g. Amazon for each relay?
> 

We are using 3rd party VPS services currently.


> *Feedback:*
> No mention of what legal entity operates this website, the domain is
> registered to an individual with obfuscated whois so I'd be skeptical 
> of
> just putting in a credit card number, more so that there is no 
> indication
> of who will process the transaction *(although looking through the 
> source
> it appears to be stripe.com <http://stripe.com>)* and no option for 
> paypal
> / IBAN transfer etc.
> 
> No IPv6 makes me sad

With regard to your feedback about the entity operating the website, 
this was honestly my biggest fear and probably
something I'll need to address sooner rather than later. Initially I 
just wanted to get something out to see if this
was really a service people would use before going through all of the 
paperwork of creating a non-profit. As you've probably
figured out by now this is not a full-time gig for anyone involved so we 
wanted to test the waters a bit before committing
100%. I suppose that based on your feedback though that the stats might 
be skewed if others are sharing your same opinion.
You are correct that we are using Stripe to process our payments. It 
might be worth it for me to add a blurb below the
form mentioning that.

Again, thank you for the feedback!


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

