From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vpmni-0005om-J0 for bitcoin-development@lists.sourceforge.net; Sun, 08 Dec 2013 22:26:10 +0000 Received-SPF: pass (sog-mx-3.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-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Vpmnh-0000vI-3s for bitcoin-development@lists.sourceforge.net; Sun, 08 Dec 2013 22:26:10 +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 rB8Lwop2050200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 8 Dec 2013 21:58:55 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 rB8LwoAP050199; Sun, 8 Dec 2013 21:58:50 GMT (envelope-from roy) Date: Sun, 8 Dec 2013 21:58:50 +0000 From: Roy Badami To: Sa?vann Carignan Message-ID: <20131208215850.GE62848@giles.gnomon.org.uk> References: <52A3C8A5.7010606@gmail.com> <1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net> <52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org> <52A4E199.3000209@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52A4E199.3000209@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 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] -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.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Vpmnh-0000vI-3s 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: Sun, 08 Dec 2013 22:26:10 -0000 > > 5) Who controls DNS for it? > > I'm not sure we'll get any change on this level. I have no idea if the > domain is in good hands, except for the fact that nothing bad happened > thus far. If anything, moving it to core developers (as intended when > the domain was registered) would make more sense IMO. But again, is it > possible, I don't know. That's an interesting question. The bitcoin.org domain is hiding behind a WhoisGuard anonymous registration. Why are we not allowed to know who this domain belongs to? Why are we being asked to trust some unidentified party? roy