"A heartbreaking tragedy of inertia & asymmetry in the Blockchain Rule Update Process, which makes it harder to upgrade Bitcoin: Due to a random accident of semantics, making the rules tighter (more restricted) is a "soft" change, while making the rules looser (less restricted) is a "hard" change
https://np.reddit.com/r/btc/comments/4n ... mmetry_in/
Another, somewhat similar post covered the topic from a slightly different angle - this time with a bit more emphasis on the computer science behind the terminology - including a brief discussion of the concepts of "covariant" versus "contravariant" types, often encountered in functional programming languages (eg, it's mentioned in some of the documentation on languages such as C# and Scala):
The tragedy of Core/Blockstream/Theymos/Luke-Jr/AdamBack/GregMaxell is that they're too ignorant about Computer Science to understand the Robustness Principle (“Be conservative in what you send, be liberal in what you accept”), and instead use meaningless terminology like “hard fork” vs “soft fork.”
https://np.reddit.com/r/btc/comments/4k ... ragedy_of/
Finally, five other posts explored possible motivations (political and economic) why Core / Blockstream insidiously prefers to force the more-dangerous kind of forks on the Bitcoin community (hint: it helps Core / Blockstream's interests, which they always put before the interests of Bitcoin users):
Reminder: Previous posts showing that Blockstream's opposition to hard-forks is dangerous, obstructionist, selfish FUD. As many of us already know, the reason that Blockstream is against hard forks is simple: Hard forks are good for Bitcoin, but bad for the private company Blockstream.
https://np.reddit.com/r/btc/comments/4t ... ckstreams/
"They [Core/Blockstream] fear a hard fork will remove them from their dominant position." ... "Hard forks are 'dangerous' because they put the market in charge, and the market might vote against '[the] experts' [at Core/Blockstream]" - /u/ForkiusMaximus
https://np.reddit.com/r/btc/comments/43 ... ll_remove/
As Core / Blockstream collapses and Classic gains momentum, the CEO of Blockstream, Austin Hill, gets caught spreading FUD about the safety of "hard forks", falsely claiming that: "A hard-fork forced-upgrade flag day ... disenfranchises everyone who doesn't upgrade ... causes them to lose funds"
https://np.reddit.com/r/btc/comments/41 ... sic_gains/
Normal users understand that SegWit-as-a-softfork is dangerous, because it deceives non-upgraded nodes into thinking transactions are valid when actually they're not - turning those nodes into "zombie nodes". Greg Maxwell and Blockstream are jeopardizing Bitcoin - in order to stay in power.
https://np.reddit.com/r/btc/comments/4m ... ftfork_is/
The real reason why Core / Blockstream always favors soft-forks over hard-forks (even though hard-forks are actually safer because hard-forks are explicit) is because soft-forks allow the "incumbent" code to quietly remain incumbent forever (and in this case, the "incumbent" code is Core)
https://np.reddit.com/r/btc/comments/40 ... am_always/" -
ydtm