From: Tom Zander <tomz@freedommail•ch>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork technical debate
Date: Tue, 06 Oct 2015 08:14:35 +0100 [thread overview]
Message-ID: <2156873.BPPaGcvT6q@garp> (raw)
In-Reply-To: <CAAS2fgRU3D7_9b=4rpG8B3HHnk_80Dw0WJTavvx5+1jFS6ZmEw@mail.gmail.com>
On Monday 5. October 2015 21.26.01 Gregory Maxwell wrote:
> On Mon, Oct 5, 2015 at 9:08 PM, Tom Zander via bitcoin-dev
>
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> > On Monday 5. October 2015 20.56.34 Gregory Maxwell wrote:
> >> (In this case, I don't even believe we have any regulator
> >>
> >> contributors that disagree).
> >
> > Regular contributor?
> >
> > Please explain how for a fork in the protocol should you only listen to
> > regular Bitcoin Core contributors?
>
> I'm providing some perspective and scope-- referencing again your
> comment about following actions-- what element of the many dozens of
> responses suggests to you that _anyone_ is not being listened to?
Have you ever been at a meeting where you didn't feel like you were being
listened to?
You get comments like;
«I respond to the technical arguments not because I believe they are
earnestly motivated, but because they provide an avenue for learning for
myself and others.»
«"there is no gridlock here» After several respected members stated there is
disagreement.
«That Mike himself continues to misexplain things is not surprising since he
has all but outright said that »[snip] Which is putting words in the mouth
of someone you disagree with.
But what really gives a lot of people here the suggestion that members of the
community that are against the softfork are not being listened to is the
simple undeniable fact that an alternative or a remedy is not even considered.
There is no code. There is no question posted by the authors which flags to
use.
Actions speak much louder than words. Read the topic of this thread!
The actions show a disregard for the many objections. Consensus is not build
by repeating again and again the arguments that you belief will convince your
debate-opponent. It is about reaching a middle ground. If either side of the
debate refuses to budge from their position, you have gridlock.
What came of the request made to PeterT to document the risks and required
changes in wallets should this soft fork continue?
Why is it soo bad to use a hardfork (with proper voting) instead of a softfork
that we are in a place that the Bitcoin Core team is willing to throw out a
lot of goodwill and show their true colours in hundreds of mails that leave
the opposing side of this debate feeling ignored and left out?
I don't feel specifically unique or special. Nobody needs to reply to this
email. I don't claim peoples time.
All I'm doing is spelling out what has been living in the back of my head, and
with me a great deal of others, about how this is playing out.
If you choose to ignore this and you force a softfork, I belief you may be
surprised at how many active players in the Bitcoin marketplace may see that
the "Bitcoin Core" team is not an ally any longer.
It is good to remember that the graveyards are filled with people that
believed to be unreplaceable.
Bitcoin will go on.
Have a nice day!
next prev parent reply other threads:[~2015-10-06 7:17 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 15:56 Sergio Demian Lerner
2015-10-05 16:39 ` NxtChg
2015-10-05 16:51 ` Luke Dashjr
2015-10-05 16:56 ` Mike Hearn
2015-10-05 17:01 ` Paul Sztorc
2015-10-05 17:33 ` Peter R
2015-10-05 17:56 ` NxtChg
2015-10-05 22:56 ` Btc Drak
2015-10-05 23:05 ` Milly Bitcoin
2015-10-05 17:35 ` Btc Drak
2015-10-06 18:23 ` Venzen Khaosan
2015-10-06 18:28 ` Venzen Khaosan
2015-10-06 19:34 ` naama.kates
2015-10-05 17:03 ` Btc Drak
2015-10-05 17:26 ` Tom Zander
2015-10-05 17:52 ` Btc Drak
2015-10-05 18:04 ` Gregory Maxwell
2015-10-05 18:33 ` Tom Zander
2015-10-05 18:50 ` NotMike Hearn
2015-10-05 17:33 ` s7r
2015-10-05 18:51 ` Tom Zander
2015-10-05 18:35 ` Gregory Maxwell
2015-10-05 19:13 ` Tom Zander
2015-10-05 19:41 ` Gregory Maxwell
2015-10-05 20:05 ` Steven Pine
2015-10-05 20:21 ` Milly Bitcoin
2015-10-06 7:17 ` cipher anthem
2015-10-06 7:20 ` Eric Lombrozo
2015-10-06 7:29 ` Marcel Jamin
2015-10-06 8:34 ` NotMike Hearn
2015-10-06 19:40 ` naama.kates
2015-10-05 20:28 ` Santino Napolitano
2015-10-05 20:35 ` Tom Zander
2015-10-05 20:54 ` Dave Scotese
2015-10-05 20:56 ` Gregory Maxwell
2015-10-05 21:08 ` Tom Zander
2015-10-05 21:16 ` Milly Bitcoin
2015-10-05 21:26 ` Gregory Maxwell
2015-10-06 7:14 ` Tom Zander [this message]
2015-10-05 21:27 ` Peter R
2015-10-05 21:30 ` Gregory Maxwell
2015-10-05 21:36 ` Milly Bitcoin
2015-10-05 21:37 ` Peter R
2015-10-06 1:37 ` Tom Harding
2015-10-06 3:20 ` Peter R
2015-10-06 3:39 ` Milly Bitcoin
2015-10-06 4:54 ` Luke Dashjr
2015-10-06 5:08 ` Milly Bitcoin
2015-10-06 5:49 ` Milly Bitcoin
2015-10-06 5:53 ` Luke Dashjr
2015-10-06 6:03 ` Milly Bitcoin
2015-10-06 22:14 ` phm
2015-10-06 5:07 ` NotMike Hearn
2015-10-06 5:33 ` Peter R
2015-10-05 19:36 ` Milly Bitcoin
2015-10-05 23:18 ` Eric Lombrozo
2015-10-06 17:28 ` Venzen Khaosan
2015-10-07 0:04 ` Sergio Demian Lerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2156873.BPPaGcvT6q@garp \
--to=tomz@freedommail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox