MIME-Version: 1.0
In-Reply-To: <C47D37EE-AE42-4175-AD6B-F6FD0841287B@gmail.com>
References: <CALqxMTFkgGx0FxMiZ77inOZSs_+TQ88Wpj-q-c12COkO9tP4gQ@mail.gmail.com>
	<CADJgMzv+cKPY9wrAzbk5pgQJS0=R9KWu-+EuppM=nmXs8RHxYg@mail.gmail.com>
	<20150819182010.GB12306@muck>
	<CADJgMzskK9iNoRzVr0BtK+XH-x2w5mGZtBiieQpwcGevnHRjGg@mail.gmail.com>
	<55D4D9C3.5070004@riseup.net>
	<C47D37EE-AE42-4175-AD6B-F6FD0841287B@gmail.com>
Date: Wed, 19 Aug 2015 21:58:55 +0200
Message-ID: <CABm2gDpAOQim63Q7r9r-Pv-K+FqizgDHNUmQ7uheGMuMt-e2QA@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Eric Lombrozo <elombrozo@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
Precedence: list

On Wed, Aug 19, 2015 at 9:48 PM, Eric Lombrozo via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> [...]
> core devs=E2=80=9D and relying on the fact that many people out there can=
=E2=80=99t seem to
> tell the difference between a source code fork and a blockchain fork.

And this is precisely why we should make perfectly clear that we're
not against a code fork where Hearn or anyone else acts as a
"benevolent dictator", just against the controversial hardfork it is
attempting to deploy.
Otherwise the PR battle is probably lost (which may mean users sell
all their BTC for XTBTC [or just forget about their BTC and only care
about their XTBTC]).