📅 Original date posted:2013-12-09
📝 Original message: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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131208/d012ed80/attachment.html>;
Jeremy Spilman [ARCHIVE] /
npub10e…jc727
2023-06-07 17:10:27
in reply to nevent1q…zmnm
Author Public Key
npub10etkvm8l0jr0jsgdx02dxnhnu5g989dnca90guj5rklwkaplnh3sgjc727Published at
2023-06-07 17:10:27Event JSON
{
"id": "160201a1bc985544fbcfa06d5276baf41d7c264d51179975c26c131459c8d46c",
"pubkey": "7e57666cff7c86f9410d33d4d34ef3e5105395b3c74af472541dbeeb743f9de3",
"created_at": 1686150627,
"kind": 1,
"tags": [
[
"e",
"d517aa463a22abef5f03468f652eeefb44676da99926537d88111078c3e0468b",
"",
"root"
],
[
"e",
"a737cec67eedcda16529b7b3d943cad936d7a9c8d6fda4f31e3b1a9799f4079b",
"",
"reply"
],
[
"p",
"cf0c36d3cbefb87dda6e830ae3e537314270c42aa31124b0838c6619e712088e"
]
],
"content": "📅 Original date posted:2013-12-09\n📝 Original message:I can provide the server hardware and colocation (space, power, and \nbandwidth) if dedicated 50Mbit in 55 S. Market, San Jose, CA data center \nis acceptable.\n\nIf it needs more bandwidth than that, in a few months I hope to be getting \nspace in LA with 1Gbit, but I can't commit to that now.\n\n\n\u003e On Sun, Dec 8, 2013, at 03:11 PM, Drak wrote:\n\u003e\u003e It's not just about trust, there is the robustness factor: what if he \n\u003e\u003e becomes sick, unavailable, hit by a bus? Others need the ability to \n\u003e\u003e \u003e\u003epickup and run with it. The control over the domain (including \n\u003e\u003e ability to renew registration, alter nameservers) needs to be with more \n\u003e\u003e than \u003e\u003eone person. That's why I suggest using the same people who have \n\u003e\u003e control over the software project at sf,github\n\u003eThe bitcoin.org domain is controlled by me, Sirius, and an anonymous \n\u003e person. Control will not be lost if Sirius becomes unavailable.\n\u003eSSL is probably a good idea, and it's probably also a good idea to \n\u003e separate bitcoin.org from Github. I don't know that I trust Github. I'm \n\u003e sure that you can \u003efind a sponsor for a dedicated server. Let us know if \n\u003e DNS changes to bitcoin.org are required.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131208/d012ed80/attachment.html\u003e",
"sig": "6818435649507c79fb5246c6505555bd5cd6d471c625325e618a15efaff0e37d07938706ee11463fd433c0bcd1023690b70c50b092b50bbc3c57376e9ecfcd06"
}