If you are anti BIP -110, the best thing you can do is HOLD CORE ACCOUNTABLE BY HAVING THEM REVERT THE RELAY POLICY TO 82 BYTES. If the inscription bug was the gasoline, that action and the unwillingness to waver on it was the match that lit the fire. The fact that the pro-core side doesn't even consider this an option is why so many people are abandoning it as the reference implementation and running a fork. Do people not realize there is easy reversal of course that would show good faith? Honestly the pro core influencers are all acting like this is a rogue element of a few bad actors. No there are a LOT of people who are fed up with Core for directly supporting spam with the change of mempool policy. Core is dying in the bed they made. Even if the fork fails, they will be dead in that bed unless they change course and listen to users with valid concerns.