Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vpvil-0003AF-LE for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 07:57:39 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of taplink.co designates 50.117.27.232 as permitted sender) client-ip=50.117.27.232; envelope-from=jeremy@taplink.co; helo=mail.taplink.co; Received: from mail.taplink.co ([50.117.27.232]) by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1Vpvik-0001Yn-Kv for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 07:57:39 +0000 Received: from laptop-air.hsd1.ca.comcast.net ([192.168.168.135]) by mail.taplink.co ; Sun, 8 Dec 2013 22:33:01 -0800 Content-Type: multipart/alternative; boundary=----------K8MZkioxga7MEVCzSdk7ly To: bitcoin-development@lists.sourceforge.net References: <52A3C8A5.7010606@gmail.com> <201312082101.25609.luke@dashjr.org> <1386546680.28932.57095933.29430EA8@webmail.messagingengine.com> Date: Sun, 08 Dec 2013 22:29:25 -0800 MIME-Version: 1.0 From: "Jeremy Spilman" Organization: TapLink Message-ID: In-Reply-To: <1386546680.28932.57095933.29430EA8@webmail.messagingengine.com> User-Agent: Opera Mail/1.0 (Win32) oclient: 192.168.168.135#jeremy@taplink.co#465 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitcoin.org] 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Vpvik-0001Yn-Kv Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org, your thoughts? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 07:57:39 -0000 ------------K8MZkioxga7MEVCzSdk7ly Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit I can provide the server hardware and colocation (space, power, and bandwidth) if dedicated 50Mbit in 55 S. Market, San Jose, CA data center is acceptable. If it needs more bandwidth than that, in a few months I hope to be getting space in LA with 1Gbit, but I can't commit to that now. > On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote: >> It's not just about trust, there is the robustness factor: what if he >> becomes sick, unavailable, hit by a bus? Others need the ability to >> >>pickup and run with it. The control over the domain (including >> ability to renew registration, alter nameservers) needs to be with more >> than >>one person. That's why I suggest using the same people who have >> control over the software project at sf,github >The bitcoin.org domain is controlled by me, Sirius, and an anonymous > person. Control will not be lost if Sirius becomes unavailable. >SSL is probably a good idea, and it's probably also a good idea to > separate bitcoin.org from Github. I don't know that I trust Github. I'm > sure that you can >find a sponsor for a dedicated server. Let us know if > DNS changes to bitcoin.org are required. ------------K8MZkioxga7MEVCzSdk7ly Content-Type: multipart/related; boundary=----------K8MZkioxga7MEVdvaYihf1 ------------K8MZkioxga7MEVdvaYihf1 Content-Type: text/html; charset=iso-8859-15 Content-ID: Content-Transfer-Encoding: Quoted-Printable
I can provide the server hardware and colocation (space, powe= r, and bandwidth) if dedicated 50Mbit in 55 S. Market, San Jose, CA data= center is acceptable.

If it needs more bandwid= th than that, in a few months I hope to be getting space in LA with 1Gbi= t, but I can't commit to that now.

On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:
It's not just = about trust, there is the robustness factor: what if he becomes sick, un= available, hit by a bus? Others need the ability to pickup and run with = it. The control over the domain (including ability to renew registration= , alter nameservers) needs to be with more than one person. That's why I= suggest using the same people who have control over the software projec= t at sf,github
 
The bitcoin.org domain is controlled by me, Sirius, and an anonymou= s person. Control will not be lost if Sirius becomes unavailable.
 
SSL is probably a good idea, and it's probably also a good idea to = separate bitcoin.org from Github. I don't know that I trust Github. I'm = sure that you can find a sponsor for a dedicated server. Let us know if = DNS changes to bitcoin.org are required.



------------K8MZkioxga7MEVdvaYihf1-- ------------K8MZkioxga7MEVCzSdk7ly--