As I said in my post:
"If you care about Bitcoin's consensus rules I'd request you pay attention so
you can make an informed view on what to run and what to support."
Ideally everyone would come to an informed view independently. Unfortunately
many people don't have the time to follow Bitcoin drama 24/7 and hence struggle
to separate noise from signal. In this case simple heuristics are better than
nothing. One heuristic is to listen to those in the past who showed good
judgment and didn't seek to misinform. Of course it is an imperfect heuristic.
Ideally the community would be given sufficient time to come to an informed
view independently on what software to run and not be rushed into making
decisions. But it appears they are not being afforded that luxury.
> I fear you risk losing respect in the community
I appreciate your concern.
--
Michael Folkson
Email: michaelfolkson at [protonmail.com](http://protonmail.com/)
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
------- Original Message -------
On Saturday, April 23rd, 2022 at 6:10 AM, Billy Tetrud <billy.tet...@gmail.com>
wrote:
>> assuming people pay attention and listen to the individuals who were
>> trusted during that period
>
> Bitcoin is not run by a group of authorities of olde. By asking people to
> trust "those.. around in 2015-2017" you're asking people to blindly trust
> authorities. This, in my strong opinion, goes against the bitcoin ethos, and
> is an incredibly harmful way to push for your agenda. I'd very much recommend
> you reassess the way you're going about what you're trying to do. I fear you
> risk losing respect in the community by implying without any evidence that
> certain people are "taking advantage" of some situation and attempting "to
> confuse".
>
> On Fri, Apr 22, 2022 at 12:33 PM Michael Folkson via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> If the next few weeks go how I fear they will it could get messy. If you
>> care about Bitcoin's consensus rules I'd request you pay attention so you
>> can make an informed view on what to run and what to support. For those of
>> you who were around in 2015-2017 you'll know what to expect. The right
>> outcome endured in 2017 and I'm sure the right outcome will endure here
>> assuming people pay attention and listen to the individuals who were trusted
>> during that period. There are always a large number of motivated parties who
>> are incentivized to break nodes off from Bitcoin and may seek to take
>> advantage of a contentious soft fork activation attempt.
>>
>> Remember that if all the information is presented to users in a clear way
>> well ahead of time then they can make their own mind up. I fear that things
>> will be made as convoluted as possible in a way intended to confuse and
>> information will be withheld until the last minute. When in doubt it is
>> generally better to rely on the status quo and tried and trusted. In this
>> case that would be Bitcoin Core. Alternative releases such as those seeking
>> to attempt to activate CTV or indeed those seeking to resist the activation
>> of CTV really should only be considered if you are informed on exactly what
>> you are running.
>>
>> If you are interested in the effort to resist the contentious soft fork
>> activation attempt of CTV please join ##ursf on Libera IRC.
>>
>> Have a good weekend. Hopefully those behind this contentious soft fork
>> activation attempt will see sense and we can go back to more productive
>> things than resisting contentious soft forks.
>>
>> --
>> Michael Folkson
>> Email: michaelfolkson at [protonmail.com](http://protonmail.com/)
>> Keybase: michaelfolkson
>> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
