{"type":"rich","version":"1.0","author_name":"npub16lyqvgruy8k0mmn9f3gqr69w0xlahmzlc6x6lq95amk6uppffm3q69pqjm","author_url":"https://nostr.ae/npub16lyqvgruy8k0mmn9f3gqr69w0xlahmzlc6x6lq95amk6uppffm3q69pqjm","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-12-08\n📝 Original message:\u003e Issues that would need to be resolved:\n\u003e \n\u003e 1) Who pays for it? Most obvious answer: Foundation. However there's\n\u003e currently a fairly clear line between the foundation website and the\n\u003e bitcoin.org \u003chttp://bitcoin.org\u003e website. I personally am fine with the\n\u003e bitcoin foundation funding the website, it's a lot closer to the bitcoin\n\u003e community than github. But some people might care. So next step would be\n\u003e to contact the Foundation board and see if they're willing to fund it.\n\nActually I might find way to fund it. But I needed to have ACK \u0026\ncomments from developers before anything.\n\n\u003e 2) Anti-DoS? I assume github handles this at the moment, though I doubt\n\u003e there's anything to be gained from DoSing the informational website\n\nThat is a fair question, we will need anti-DDoS. Unless something better\n(and affordable) can be recommended, this would yet put another Bitcoin\nwebsite under CloudFlare.\n\n\u003e 4) Who admins it?\n\nObviously, I thought it would be important that the server is owned by\nsomeone who can be trusted, with ssh access for all core developers.\n\n\u003e 5) Who controls DNS for it?\n\nI'm not sure we'll get any change on this level. I have no idea if the\ndomain is in good hands, except for the fact that nothing bad happened\nthus far. If anything, moving it to core developers (as intended when\nthe domain was registered) would make more sense IMO. But again, is it\npossible, I don't know."}