segwit has made it so bitcoin can be forked and/or upgraded far more easily without having to achieve a 95% consensus before features activate
LIE.Any fork can be activated at any threshold. It depends what code those securing the chain choose to run.
For hardforks, you are more than welcome to run software that sets activation at 95% if that's what you want. But if enough users are running code that allows a fork to activate at a lower threshold, then that's what will happen. There is no rule that states it always has to be 95%.
For softforks, you are more than welcome to run software that doesn't support the fork at all. But if you've made the choice to do that, then you accept the consequences that you may need to trust others that did choose to support the fork. Much like you accept the consequences that you need to trust others if you choose to run an SPV client. Run what you want, but understand what the implications are.
You don't get to dictate that forks can't activate with a lower threshold. Users are free to decide this for themselves.
again you are misguided.
1. im not dictating crap. thats what the "dev state" done in august 2017
2. consensus of majority means just that. majority.. by the "dev state" wanting a lower threshold is a contentious fork
3. by making nodes get banned and blocks getting rejected is also a different scenario than consensus.
the old consensus mechanism would not ban old nodes and would not ban old block formats..
but the dev state you support have and did..
4. by promoting such threatening contentious fork which occured on august 1st. was not consensus
but atleast your starting to admit that core are running code that activates at a lower threshold...
you finally tripped over your own flip flop which goes against your previous flips of 100% loyalty
anyway my argument is not about the %. its about the fact that it was not a clear majority accrued via full community count. due to the tricks of NYA/UASF/"compatibility" etc...
i already told you in many topics "mandatory" "mandatory" "mandatory" "mandatory" is what i am against.
you keep saying how users get to choose by them upgrading to a feature they want. yet segwit wasnt not activated by the method you flip.. you even admit the "compatibility. and the no vote and the other stuff that users dont get to dictate what core should do... so no point you flopping by suddenly saying users do get a vote
now may you go in peace and watch some eastenders. because i know you love your soap opera/drama more so that reality