Really disappointed to hear that. Read BIP 444 for yourself. Written by Luke but submitted under a new nym and a new github account to mislead people. It creates a "soft fork" that grants them chain rollback power. They are lying about it being a soft fork. If they never rollback no point activating it. If they do rollback it is a hard fork from the people who don't, no way around that.
Login to reply
Replies (5)
I read it. I didn't think that's what it said.
"If, however, some content appears in the chain that causes significant risks, we can fall back to the reactive method, which is a retroactive chain reorganization to invalidate the offending block (and any subsequent blocks) while immediately activating the new rules."
From

GitHub
BIP 110: Reduced Data Temporary Softfork by dathonohm · Pull Request #2017 · bitcoin/bips
Mailing list thread at https://groups.google.com/g/bitcoindev/c/nOZim6FbuF8
Editor note: please post conceptual feedback and meta-commentary on th...
A fork also complicates and breaks some things with lightning. I'm guessing a lot of node runners who are advocating for Bitcoin Cashjr haven't considered this part yet.
View article →
Welllll actually, for me at least, I've counted that as a plus. I'm no expert on lightning, but I find it hard to believe it couldn't work without taproot.
It can work but it is more private with taproot. Not the first time Luke's solutions are bad for privacy.