Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of mm.st
	designates 66.111.4.28 as permitted sender)
	client-ip=66.111.4.28; envelope-from=theymos@mm.st;
	helo=out4-smtp.messagingengine.com; 
Message-Id: <1386546680.28932.57095933.29430EA8@webmail.messagingengine.com>
From: theymos <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_1386546680289320"; 
	charset="utf-8"
Date: Sun, 08 Dec 2013 17:51:20 -0600
In-Reply-To: <CANAnSg0vwbSyYtzOpbFzaHmS2wQ2aQCibk9tg+G4VA_ESp_7ow@mail.gmail.com>
References: <52A3C8A5.7010606@gmail.com>
	<CAAS2fgT2x3iLnRiLabPT28eO6rbGuBBgi2s-Yhtgwo+3XWq7+Q@mail.gmail.com>
	<CANAnSg3GeLPyXXK5Osg1hcC7MQ=Na3BWrGCe95ab7UcbeG2Jgw@mail.gmail.com>
	<201312082101.25609.luke@dashjr.org>
	<CANAnSg0vwbSyYtzOpbFzaHmS2wQ2aQCibk9tg+G4VA_ESp_7ow@mail.gmail.com>
Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org,
 your thoughts?
Precedence: list

This is a multi-part message in MIME format.

--_----------=_1386546680289320
Content-Transfer-Encoding: 7bit
Content-Type: text/plain

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.

--_----------=_1386546680289320
Content-Transfer-Encoding: 7bit
Content-Type: text/html

<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div><div><div>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<br></div>
</div>
</div>
</div>
</blockquote><div dir="ltr"><div><div><div>&nbsp;</div>
<div>The bitcoin.org domain is controlled by me, Sirius, and an anonymous person. Control will not be lost if Sirius becomes unavailable.<br></div>
<div>&nbsp;</div>
<div>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.<br></div>
</div>
</div>
</div>
</body>
</html>

--_----------=_1386546680289320--