Delivery-Date: Fri, 17 Apr 2015 16:39:20 -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=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY,
	URIBL_RHS_DOB 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 727B71E0CB2
	for <archiver@seul.org>; Fri, 17 Apr 2015 16:39:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A49AC21013;
	Fri, 17 Apr 2015 20:39:14 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8658420ED3
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 20:39:11 +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 u63XNlRM838E for <tor-talk@lists.torproject.org>;
 Fri, 17 Apr 2015 20:39:11 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 52F7120EC0
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 20:39:11 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 7669D411B7
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 20:39:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1429303148; bh=wPdopZ3HuPFQi4soKZl0CVWhaXKKNlRiy/us75ubnhI=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=sfgXqOWPf0CpPdModiBdduosPyY8poGR/b6Id7U1d5Bc3P0BSUQedq+/IxI8i89CG
 jJAZ4WDygzZQYyoFnXnWcJFUcyU+d9anhrAvZDsdpUTMJpN8262SwxiZ3o/xy6rWHY
 2j7/BELgZw3ZpfX7NHYRQNA70GleHX+FecDkxflE=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: when2plus2is5) with ESMTPSA id E806F22C6D
Message-ID: <55316F66.5080806@riseup.net>
Date: Fri, 17 Apr 2015 20:39:02 +0000
From: Speak Freely <when2plus2is5@riseup.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <710b761efa7d892ff39b9a6394b5b2a3@sponsor-privacy.com>
 <553160A6.4010508@openmailbox.org>
 <b5e8df4dfdc51443220a5cda4a3c9902@sponsor-privacy.com>
In-Reply-To: <b5e8df4dfdc51443220a5cda4a3c9902@sponsor-privacy.com>
X-Virus-Scanned: clamav-milter 0.98.6 at mx1
X-Virus-Status: Clean
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

For $65/year I'll be able to do 380MB/s (1000TB/month)?

Sign me up!


Matt
Speak Freely

social@sponsor-privacy.com:
> On 2015-04-17 13:36, nusenu wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Thanks for your effort.
>>
>> - From a "customer" perspective I'm missing some crucial information on
>> your website:
>> - - what bandwidth (mbps or TB per month) does this relay add to the
>> network? (I understand that it is hard to estimate but if the data
>> plan allows only lets say 1TB per month you should make that clear)
>> - - am I adding an exit or non-exit relay?
>>
>>
>> More experienced "customers" might want to know:
>> - - What characteristics has the relay? how much memory?
>> - - Where are you going to run the sponsored relay?
>>     AS? Country? hosting provider?
>>     from your first relay: AS393406, US, Digital Ocean
>> - - What OS are you going to use? (apparently Linux)
>> - - Can I select location/OS/bw/.. ?
>> - - Do you provide bw monitoring and traffic stats? (i.e. munin and
>> vnstat
>> )
>> - - Can I choose to run 2 instances per server? (which results in more
>> traffic)
>>
>> I understand that you might want to keep this website simple since you
>> target non-technical persons but providing that information wouldn't
>> hurt. It doesn't have to be on the main page.
>>
>>
>> I hope you also consider the following points:
>>
>> - - proper automatic MyFamily configuration on all your relays
>> - - keep your relays up to date
>> - - network and platform diversity (this becomes more relevant once you
>> run a substantial part of the tor network)
>>     - run relays in non-top x countries/ASes/... by consensus weight
>>         https://compass.torproject.org
>>     - run non-Linux relays
>>         https://metrics.torproject.org/platforms.html
>>
>>
>> Do you "pre-run" relays and rename them as soon as they are "ordered"
>> to reduce the bootstrap phase?
>>
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>>
>> iQIcBAEBCgAGBQJVMWClAAoJEFv7XvVCELh0aa0P/A/8PpBHnF6o1i0x/cXJHOj7
>> UrWwZARNBpeIWrov2vs/3TsDEABEQiEe6/c4UIKrzYvJbAssEH6AyoWcfARCv+uo
>> zwU9HXdty7VZZDIqOTLBi7YZ+1ri1EEW8/ZhUOwk/aETgOVSrQE3BDbzmVZaqWbp
>> 94cReiR9lbRH2CJGPP0Eo5WzLImTN/Qo70kmUZ8bJRYK1VyWhZ27+c5bI8cKu8/Y
>> OxoTZRr7MkKH1egPE6+c8lo1vruysHjN9ZWHWmGkZeREQw7ZYk4WaoCD6fq0awFX
>> TK+I2T/ePgHUegR8jdPB2n60F2KYjC47ATPO7cXyO+Lgo6foqppNFti8V1a9pJja
>> SKuP5Cgy98lgHheGMwphu33k5yjWg3B8Nkv0tgDQh/dprYaQGLqGLRxGpqCXrl3l
>> nMLbHungWsIZtdrLb+hmxJIpUFcBrnAZmSuHa0W2sV5uatup2ndOAxjPOZ4iLwRg
>> 8wYUBQP4Z5MtQI8ECTZkd4FTj9jOMbg7768zqaLeNK/HOxbrCViY5cjmhIckhcit
>> iiTrWYWtksk2X4/tbh+OenUeyBLiSbB/6aYADylVR08fEoFPh3cGT5e8eHUaO1sp
>> tBUvpPo1Hq39gd5K+BElO9AKl/q++RuL5QpPWVwYDdyguyymvsd4lFx3o4kEm+me
>> j8GCv9tpkKSDnj3jcxFE
>> =zA/v
>> -----END PGP SIGNATURE-----
> 
> Appreciate the feedback. As you noted the primary target was someone who
> might not know really what bandwidth is, how much memory, etc but I can
> see your point where some potential customers might like to have that
> information. If nothing else it might help validate the $65 cost. I'll
> try to answer some of those questions here and think about how the info
> could be integrated into the site itself.
> 
> - Bandwidth: the instances being used come with 1000TB per month. This
> has been set as the cap in the torrc file so each instance can in theory
> use all 1000TB before it stops passing traffic.
> 
> - The instances are currently being setup with DigitalOcean which does
> not allow exit relays so only non-exit relays are being created.
> 
> - Each relay is SSD based (20gigs), comes with 1 "cpu" (these are
> virtual instances) and 512mb of RAM
> 
> - Currently all instances are provisioned in the United States but the
> plans are to use every DC that DigitalOcean has available which means
> with a minor change to the code instances could also be deployed in the
> Netherlands, Germany, England and Singapore. Eventually the goal is to
> bring in other providers outside of DigitalOcean to expand the possible
> footprint.
> 
> - You are correct, the OS is Linux :)
> 
> - We do not provide any stats at this time. Something that has been
> discussed though was a possible page that showed all relays customers
> had sponsored with some bandwidth stats next to them. It would be more
> of a novelty than anything, nothing for real system type monitoring.
> 
> - As far as running two relays on one instance, that is not an option
> right now. The way it works is there is an image I created that is a
> basic Linux image with the Tor client installed. When someone sponsors a
> relay through the site an API call is made to spin up a new instance
> based on this image. During the API call some cloud-init data is passed
> to a small script on the image which handles setting up the torrc file
> with the correct relay name and contact notes. At that point a new
> fingerprint is generated and the Tor client is restarted. Since these
> are SSD based the time from payment to running is typically about a
> minute assuming everything behind the scenes at DigitalOcean is happy.
> It would certainly be possible to run two relays on a single instance
> but would introduce a bit more complexity that I'll need to look into.
> 
> - In all honesty, the MyFamily option is something that I didn't think
> would really apply to this as the goal is to never actually login to
> these boxes. I do see though how that could make people feel uneasy
> since technically SponsorPrivacy will be the "owners" of all of these. I
> will bump that to the top of the TODO list so we can start dynamically
> updating that setting as new instances are provisioned. Consider that
> the first bug :)
-- 
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

