He had every right to object to a disruption of existing and appropriately risk-managed 0conf use cases.

Especially so when core contributors were also projecting an explicit desire to turn the default to ON in a future release on the back of its introduction.

I disagree that this isn’t related. Both situations are examples of pushing aside well articulated critique to achieve a false sense of consensus.