Do you think freedom is one of Bitcoin's most important qualities? Or is it more important that we ensure everyone is happy and agrees with any changes? If you had to choose, which takes priority? Freedom? Or ensuring everyone agrees?
they don't have to be on two different sides. the freedom is the most important thing but also since we are in a decentralized system everyone should agree about a change or that change must not happen if they can't reach an agreement.
Do you think "consensus" should always mean a hardfork at 95% agreement? Even if that means that just 6% of the network can then effectively veto any changes and stagnate progress? Or are softforks perfectly acceptable as well? How do you feel about users who express the belief that softforks effectively turn them into second-class-citizens if they don't want to to upgrade? Do they have cause to complain? Or is the fact that they can remain on this blockchain and continue transacting as they always have done a sufficient compromise? Is it right for some users to move forward with a change if others haven't given their permission for that change? Does this weaken or bypass consensus?
i don't like playing with terms like "soft/hard fork" i believe they mislead the arguments. i say any change in consensus rules must only happen with the majority's support and if that can not be reached then that change must not happen. otherwise we do not have a healthy decentralized system.
so far all the bitcoin "changes" have happened with this kind of majority support (over 95%) and that is why bitcoin is still strong and has not split into more than 1 chain.
and that is why i strongly hate bitcoin-cash which never had any support, clearly visible based on their initial hashrate and lack of usage in the past year.
this is also why i hate things such as BIP148 and all those who were misleading people at that time like LukeJr.
Is it wrong or immoral to create code that causes a client to disconnect another client from the network if the features they propose are not compatible? Should users be allowed to disconnect incompatible clients if they want to? Or is this a way to cheat consensus and deprive the users running that client of the chance to express their support for a change in the rules? And, in this morality judgement, should we consider whether replay protection is included in the the client being disconnected if that means users can be safeguarded from replay attacks?
there are two different discussions here:
1. disconnecting from a client that is following different consensus rules
2. disconnecting from a client that is following the same consensus rules but is just different
the first one is a must and it should happen automatically too, like disconnecting from BCH nodes in August when the fork first happened.
but the second one is a dishonest and dirty move. like disconnecting from btc1 nodes that were enforcing the same consensus rules but were being banned months before the deadline of the 2 MB hard fork came.
If you run a full node, are you fully aware of what rules it enforces? Do you keep up to date with the latest changes? Do you compile the code yourself so you know exactly what is going on? Or do you blindly update your node without checking what the code actually does?
it is impossible for everyone to go through the code or even compile it themselves. but i believe that people should at least read the change log to be aware of what is being changed. new versions are not just new features, there are bug fixes too that may be influencing you.
Most important of all, does anyone genuinely believe Core are "in control" of the Bitcoin network? Or do you think those securing the chain (both non-mining full nodes and miners) are ultimately the ones who make the decisions? Do you think some developers have too much influence? Should there be a larger number of dev teams? Does Bitcoin have a level playing field?
no i don't believe that but they certainly have a big influence as they should since they have the experience coming from years of working on bitcoin and that doesn't have to be a bad thing. although i have seen a bad mentality grow in the past couple of years, specially in 2017. for example by that time if you asked those who were passionately against BClassic, BCH, SegWit2x,... and were supporting SegWit or even UASF why they are against the first and for the second they would have answered because core is not/ supporting it. and that is a dangerous thing.
i still believe that we need multiple implementations of bitcoin that are preferably written in a different language by different teams so that they don't have the dependency which would also prevent problems like
this one, although you can read the discussions against something like that in this topic too but i still believe the benefits are more..