From mboxrd@z Thu Jan 1 00:00:00 1970 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 1Z5YCE-00066T-Bp for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 11:41:26 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Z5YCC-0003Uy-7N for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 11:41:26 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Z5YC1-0000mQ-4I for bitcoin-development@lists.sourceforge.net; Thu, 18 Jun 2015 13:41:13 +0200 Received: from 2-228-102-98.ip191.fastwebnet.it ([2.228.102.98]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Jun 2015 13:41:13 +0200 Received: from lawrence by 2-228-102-98.ip191.fastwebnet.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Jun 2015 13:41:13 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Lawrence Nahum Date: Thu, 18 Jun 2015 11:41:01 +0000 (UTC) Message-ID: References: <55828737.6000007@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 2.228.102.98 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/43.0.2357.81 Chrome/43.0.2357.81 Safari/537.36) X-Spam-Score: -1.8 (-) 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.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Z5YCC-0003Uy-7N Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers 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: Thu, 18 Jun 2015 11:41:26 -0000 Mike Hearn plan99.net> writes: > It's the only way to keep a project making progress at a reasonable pace. [SNIP] If Bitcoin is managed with a linux kernel style dictator it would be centralized (yet unlike linux, where people can fork without impacting others in Bitcoin a hard fork puts at risks everyone's bitcoins) - I hope we all agree there is no point in a centralized Bitcoin? In addition and more importantly, it would put Gavin in tremendous dangers, both from violent threats/blackmailing prospective as well as regulatory prospective - how can you not see that? I hope all this confrontation will be worth something in the end: to show that Bitcoin can't be changed centrally and that it can't be changed without consensus