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..
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.
old nodes are not compatible. they are handed a pidgeon english translation.. theres a difference
its why even the devs clearly pointed out that old nodes become downstream/filtered(their buzzwords) nodes instead of part of the main relay network. they even drew a picture to make it easy to understand.
old nodes do not relay blocks to segwit nodes nor relay segwit transactions. they only receive a stripped down block and then sit on the edge of the network
old nodes are handed stripped data to BYPASS a consensus mechanism that would otherwise have gotten segwit blocks rejected
thats why luke JR done what he done. it was not a softfork in a sense of consensus. it was a bypass to avoid a consensus event. luke JR even said so himself that it bypasses the requirement of a consensus
but the funny part is. because they didnt get 95% through the "compatibility" trick.. and for months they only sat at 35-40% they needed to then do a mandatory threat eviction trick to FAKE getting 95% by literally ignoring/rejecting opposers.
that is like apartheid. not giving the whole community a vote and ignoring a certain side of the community and only counting those that agree..
the fair, level playing field solution would have been to realise they were not getting it. and then recode a bip that included what the whole community would have been happier with. and thus not need to mandate anything
anyway
if you actually look at the data a old node gets. and that it no longer fully validates all data but just blindly passes things.. you will see the shoddy crap. if it was compatible then old nodes would be on par and same level.. you know still relaying full data and validating full data
old nodes dont get full data. they dont get the now full true blockchain. trying to say they are "compatible" is downplaying how old nodes are not actually full validating/archiving nodes of full true data. if you truly think old nodes are compatible and same level playing field then you need to do some serious research. and not just from buddies who just repeat the same story. but actually get the data and look at it
dang all these core defenders cant be assed to even look at code or data and just wanna protect a dev.. even if its at the cost of just letting the network not excel..(facepalm)
its becoming funny how you lot are protecting certain devs, even if you have not read or understood what the devs you protect have actually admitted to. which adds more proof you lack research and are just trying to cause social drama for entertainment.
maybe its time you lot spend more time understanding and reading data, statistics and researching what actually happened and care more about the effects it has on the network. and less time just chatting about what you think the dev you protect wants.
care about the network. not a person and especially not a person you have not researched to even know what they actually said
anyway. your meanders to turn topics into 'protect a dev' are foolish. so spend some time researching. and maybe one day you will actually start to care less about devs and care more about the network