<oembed><type>rich</type><version>1.0</version><author_name>npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_name><author_url>https://nostr.ae/npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</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 8 December 2013 21:01, Luke-Jr &lt;luke at dashjr.org&gt; wrote:&#xA;&#xA;&gt; On Sunday, December 08, 2013 8:51:07 PM Drak wrote:&#xA;&gt; &gt; Otherwise, who has admin rights to the code projects&#xA;&gt; &gt; (github/sourceforge/this mailing list)? Those people have proven they can&#xA;&gt; &gt; be trusted so far.&#xA;&gt;&#xA;&gt; Can someone explain how Sirius has proven the least bit untrustworthy?&#xA;&#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 pickup&#xA;and run with it. The control over the domain (including ability to renew&#xA;registration, alter nameservers) needs to be with more than one person.&#xA;That&#39;s why I suggest using the same people who have control over the&#xA;software project at sf,github.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131208/232210d7/attachment.html&gt;</html></oembed>