<oembed><type>rich</type><version>1.0</version><author_name>npub10vt6y7m6shn8hfuj83zjlwcga4fky38kv73qz6xlcvtj4q7fjt0sqmper0</author_name><author_url>https://nostr.ae/npub10vt6y7m6shn8hfuj83zjlwcga4fky38kv73qz6xlcvtj4q7fjt0sqmper0</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-12-08&#xA;📝 Original message:On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:&#xA;&#xA;It&#39;s not just about trust, there is the robustness factor: what if he&#xA;becomes sick, unavailable, hit by a bus? Others need the ability to&#xA;pickup and run with it. The control over the domain (including ability&#xA;to renew registration, alter nameservers) needs to be with more than&#xA;one person. That&#39;s why I suggest using the same people who have control&#xA;over the software project at sf,github&#xA;&#xA;&#xA;The bitcoin.org domain is controlled by me, Sirius, and an anonymous&#xA;person. Control will not be lost if Sirius becomes unavailable.&#xA;&#xA;SSL is probably a good idea, and it&#39;s probably also a good idea to&#xA;separate bitcoin.org from Github. I don&#39;t know that I trust Github. I&#39;m&#xA;sure that you can find a sponsor for a dedicated server. Let us know if&#xA;DNS changes to bitcoin.org are required.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131208/576e4afb/attachment.html&gt;</html></oembed>