Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XL89h-0007Ce-43 for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 10:02:41 +0000 X-ACL-Warn: Received: from nl.grid.coop ([50.7.166.116]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XL89R-00060Z-Ho for bitcoin-development@lists.sourceforge.net; Sat, 23 Aug 2014 10:02:41 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by nl.grid.coop with local; Sat, 23 Aug 2014 00:53:12 -0500 id 000000000006E26C.0000000053F82C48.00004CDB Date: Sat, 23 Aug 2014 00:53:12 -0500 From: Troy Benjegerdes To: Wladimir Message-ID: <20140823055312.GO22640@nl.grid.coop> References: <20140820012623.GN22640@nl.grid.coop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: 0.8 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.4 NO_DNS_FOR_FROM DNS: Envelope sender has no MX or A DNS records 1.1 DATE_IN_PAST_03_06 Date: is 3 to 6 hours before Received: date -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline X-Headers-End: 1XL89R-00060Z-Ho Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Reconsidering github 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: Sat, 23 Aug 2014 10:02:41 -0000 On Wed, Aug 20, 2014 at 08:24:33AM +0200, Wladimir wrote: > On Wed, Aug 20, 2014 at 3:26 AM, Troy Benjegerdes wrote: > > > If bitcoin wants to become irrelevant, then by all means, continue to > > depend on github and all the unknown attack surface it exposes. > > > > Those of us that do run our own servers will migrate to higher quality > > alternatives. > > So that means you're volunteering to run a web-accessible mirror of > the bitcoin repositories? > > Wladimir http://bitspjoule.org/hg/upstream/bitcoin I guess I should update it more than every 6 months and then the updates won't take so long. It would also go a lot faster if I had a couple of dedicated servers, but that won't happen until I sell someone a support contract for crypto-commodities trading. I figure a bitcoin a month should support the hardware, 24x7 monitoring, and maybe a couple of full nodes running on the servers as well. And to pick up from another comment on this thread if you don't understand some of the differences between git and mercurial, or how to set up servers that pull from git and mirror to mercurial, you will have a lot harder time tracking down and removing malicous code that could get injected if someone gets root on a Github server. It is also a very usefull excercise in distributed systems design to understand how distributed revision control systems in theory converge to a coherent global state, and what is similiar or different to Bitcoin's global consensus model of what the balance of every bitcoin address is.