{"type":"rich","version":"1.0","author_name":"npub10vt6y7m6shn8hfuj83zjlwcga4fky38kv73qz6xlcvtj4q7fjt0sqmper0","author_url":"https://nostr.ae/npub10vt6y7m6shn8hfuj83zjlwcga4fky38kv73qz6xlcvtj4q7fjt0sqmper0","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-12-08\n📝 Original message:On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:\n\nIt's not just about trust, there is the robustness factor: what if he\nbecomes sick, unavailable, hit by a bus? Others need the ability to\npickup and run with it. The control over the domain (including ability\nto renew registration, alter nameservers) needs to be with more than\none person. That's why I suggest using the same people who have control\nover the software project at sf,github\n\n\nThe bitcoin.org domain is controlled by me, Sirius, and an anonymous\nperson. Control will not be lost if Sirius becomes unavailable.\n\nSSL is probably a good idea, and it's probably also a good idea to\nseparate bitcoin.org from Github. I don't know that I trust Github. I'm\nsure that you can find a sponsor for a dedicated server. Let us know if\nDNS changes to bitcoin.org are required.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131208/576e4afb/attachment.html\u003e"}
