{"type":"rich","version":"1.0","author_name":"npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","author_url":"https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-12-08\n📝 Original message:On Sunday, December 08, 2013 9:03:38 AM Saïvann Carignan wrote:\n\u003e Binaries:\n\u003e Sourceforge is not encrypted, actually. Although binaries hosting /\n\u003e sharing could be a separate subject discussed later I think.\n\nEncryption is useless here. We want everyone to be able to download Bitcoin \nclients. Binaries on sourceforge are signed by multiple parties using gitian.\n\n\u003e Decentralization:\n\u003e So long as we actually use DNS, the website is centralized :( However,\n\u003e its content isn't (can be forked on GitHub), but regarding the domain\n\u003e name, there is not much we can do against this AFAIK.\n\nSo long as someone has root (or a user that can modify it), the website is \ncentralised. To really solve this, we would need a dedicated server that \naccepts commands only when signed by N-of-M parties, inside a cage locked by \npadlocks with keys held by independent parties, with a SSL certificate issued \nby an authority that has multiple parties watch it every step of the way into \nthat server.\n\nLuke"}