Tell me, what makes you think users and miners can't do what gmaxwell described? Show me in the code where it says that users and miners can't change the activation threshold for a fork. Oh right, you can't, because the code can change depending on what people run.
here you go. forgetting your own "compatibility" flip flops
nodes that are "compatible" did not get to opt-out. they were sheepishly treated as accepting without option
those that chose to use nodes that oppose and want something else were thrown out.
(block rejections) (ban node)
consensus is not about rejecting blocks/banning nodes.
consensus is about having proposals. and those proposals only activate when there is majority community agreement
banning nodes and rejecting blocks first is not consensus. its about apartheid. (splitting the community and only accepting votes from one side) to fake a consensus
EG apartheid analogy
july 2017: 2 black people, 4 mixed race, 4 white people on a bus.
august1st 2017: get the 2 blacks off the bus and then not be concerned about the 4 mixed race
mid august: get the bus driver to count the votes of white people who want only white people on a bus.(4/4)
november 2017: now buses are only for white people
july 2017: 20% nonsegwit, 45% compatible, 35 segwit ready.
august1st 2017: get the 20% nonsegwit off the network and then not be concerned about the 45% compatible
mid august: get the corecode to count the votes of segwit1x flag who want only segwit1x on the network (35/35=100%)
november 2017: now the network only has segwit1x
remember 45% "compatible" were not voting. they were sheeped as abstainers