"It’s not a taproot exploit" how do you want me to read this differently?
Discussion
the exploit is not related to taproot
without the upgrade masquerading jpg's in "datacarriersize" wouldn't be possible (afaik) and that's prett much what Ordinals do by obfuscating their spam inside OP_FALSE and OP_IF patterns instead of using the standardized OP_RETURN. Knots v25.1 has the potential to fix this.
He's saying "Arbitrary data on the block chain" wasn't enabled by taproot as many other methods exist, whether or not arbitrary data should be encouraged/discouraged is a controversial ongoing discussion and blaming the Taproot softfork is looking at the situation wrong.
Historically arbitrary data has always been discouraged and Bitcoiners should remain vigilant so it remains so🥳
Let him speak for himself