pull down to refresh
Ah, that makes more sense now. Haven’t really had time to dive into the details lately. Thanks for clearing that up!
reply
Most of this is clearly formulated by Mechanic in his last AMA. It's less about the spam, more about the "them". For example:
If BIP110 is not adopted by the industry who resoundingly ignore it then I'd happily say good bye to them rather than capitulate and try something else from within.
That is 100% Iatrogenesis. You create/elevate the problem, then you create a cure, then you blame everyone that doesn't take the cure. Sounds familiar from something in recent history that fucked everyone?
reply
COVID ~lol
reply
Brilliant 👏
reply
The problem is this: it can happen any time though a natural occurring race or block withholding. It can also happen due to a consensus bug (like nondeterministic outcomes between different hardware architectures, or one of those mystery CPU circuit decay errors Google found to happen with 1 in a couple million Intel CPUs)
However, that is not the case here: this is programmed to split, regardless of safety measures, just a flag day bang. I think that a bunch among us that watched the cringe of the BU crap going down (which also started as a softfork), feel that when it is intentional like that, and no reasonable measures are taken to build consensus (our way or the high way) then that is not the same thing as some bug or faulty hardware or natural occurring race.
In the end, consensus is formed between humans, the machines just reflect (when not buggy) the choices the humans made. And in this case, there are humans trying to find out how far they can push things, regardless of safety, and worse, spreading a lot of FUD. They put their novel idea of what consensus should be before the existing consensus that is. It's okay to disagree and fork off. But then just be clear about what you're doing. But this being a power struggle more than an actual improvement to bitcoin prevents honesty.