what you both have yet to research is that the august event was not a level playing field consensus vote
those that did not upgrade to latest segwit node to 'opt-in' were treated not as a no vote. but as a second class (downstream/filtered) wallet which had no power to object.
they were not allowed to reject/ban segwit blocks. instead they were handed pidgeon english voting cards that read as if nothing has changed. basically lied to about what consensus is and had no vote..
those that did not upgrade to latest segwit node to 'opt-in' were treated not as a no vote. but as a second class (downstream/filtered) wallet which had no power to object.
they were not allowed to reject/ban segwit blocks. instead they were handed pidgeon english voting cards that read as if nothing has changed. basically lied to about what consensus is and had no vote..
segwit was a soft fork. soft forks are compatible with the current consensus since they merely add compatible rules. at the node level, you can't "vote no" on a soft fork because your node already considers it compatible (assuming miners are enforcing it).
that's why older versions are completely compatible with segwit. it's a matter of network protocol, not "voting". as such, it makes no sense to view legacy nodes as "no votes". legacy nodes are opted into the consensus already, and segwit was compatible with the consensus.
also, about this "voting" shit: consensus is not democratic. it's not a "voting" system. you either opt in to the consensus by running a node, or you opt out of the consensus by shutting down your node and leaving the network. running an incompatible node = opting out. you can fix your node to reject segwit blocks. but you'll be opting out of the consensus.
