Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VpyUG-0003NT-Ug for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 10:54:52 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gnomon.org.uk designates 93.93.131.22 as permitted sender) client-ip=93.93.131.22; envelope-from=roy@gnomon.org.uk; helo=darla.gnomon.org.uk; Received: from darla.gnomon.org.uk ([93.93.131.22]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VpyUD-00014c-ET for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 10:54:52 +0000 Received: from darla.gnomon.org.uk (localhost.gnomon.org.uk [127.0.0.1]) by darla.gnomon.org.uk (8.14.3/8.14.3) with ESMTP id rB9AsbAA057751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 9 Dec 2013 10:54:42 GMT (envelope-from roy@darla.gnomon.org.uk) Received: (from roy@localhost) by darla.gnomon.org.uk (8.14.3/8.14.1/Submit) id rB9AsawY057750; Mon, 9 Dec 2013 10:54:36 GMT (envelope-from roy) Date: Mon, 9 Dec 2013 10:54:36 +0000 From: Roy Badami To: theymos Message-ID: <20131209105435.GG62848@giles.gnomon.org.uk> References: <52A3C8A5.7010606@gmail.com> <201312082101.25609.luke@dashjr.org> <1386546680.28932.57095933.29430EA8@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1386546680.28932.57095933.29430EA8@webmail.messagingengine.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitcoin.org] X-Headers-End: 1VpyUD-00014c-ET Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org, your thoughts? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 10:54:53 -0000 > The bitcoin.org domain is controlled by me, Sirius, and an anonymous > person. Control will not be lost if Sirius becomes unavailable. I know this will be a controversial viewpoint in some quarters, but I'm not a fan of anonymity, or of pseudonyms. As far as I know (please correct me if I'm wrong) all the core devs go by their real names with the exception of Satoshi (and I would hope he no longer has commit access? - only because I would hope that no-one has pseudonymous commit access these days). I don't see why this should be different for the domain, the DNS and the rest of the infrastructure... Although that's separate from the question of who the registrant of the domain should be (the registrant being the closest thing a domain has to a recorded legal owner). Who currently purports to be the current legal owner of the domain? IMHO the registrant should obviously be real and not WhoisGuard - anonymous stuff like this always looks shady. And surely the Bitcoin Foundation is the obvious candidate to own the domain (just like kernel.org is owned by the Linux Foundation). But this may all be moot unless the current legal owners are willing to assign the domain... roy