Unfortunately, it already happened since more than a decade ago. Some of those method doesn't require miner to manually add the TX either.
Someone is not paying attention here. BIP110 doesn't aim at stopping all spam of all kinds. It aims at stopping contiguous data. Your examples are not contiguous data. A mere link to something is not a file stored on chain.
--snip--
3 source i mentioned clearly says the illicit/controversial isn't only link. Besides, i'm talking about past action.
Wikileaks cablegate data
A 2.5 megabyte Wikileak files ('cablegate-201012041811.7z') was embedded in the Bitcoin blockchain. The data is followed by a message explaining how to access it.
The remaining instance is an image depicting mild nudity of a young woman. In an online forum this image is claimed to show child pornography, albeit this claim cannot be verified (due to ethical concerns we refrain from providing a citation). Notably, two of the explicit images were only detected by our suspicious transaction detector, i.e., they were not inserted via known services.
Just days after its official debut, bitcoin (BTC) protocol Ordinals encountered a shock porn image dubbed “goatse,” inscribed into the blockchain through the protocol on Feb. 2.
According to official reports from Ordinals creator Casey Radarmor, the picture was embedded on inscription 668, appearing on Ordinals’ front page for approximately half an hour before the protocol’s devs manually took it down.
The image is on the blockchain network but has since been desynced from appearing on Ordinals’ website. However, users or anyone running the Ordinals can view and access the image.
While also give headache to both wallet developer and user (who manually specify all outputs).
It"s only a mild nuisance if you have a low balance near the dust limit. And if you want to construct yoyd own txs manually, that is your own choice to make things more complicated for yourself.
I'm talking about adding complexity to wallet developer, considering some wallet that support Bitcoin are lagging behind to support advance feature or new address format. On user side, they may never realize the change or find it's not logical.
OK, so you admit you don't know what regtest is or how it works or what it's point is.
Stop your bitching. Show me the mempool.space link to the actual transaction in question. There is a very insidious reason why all the hit pieces that talk about it don't provide a link to the actual transaction in any explorer.
Also not required but I'd really like to see the block you mined with a couple of Knots nodes. That'd be fun.
regtest network only exist on your device. So besides mining on your own regtest, you also need to self-host mempool.space and configure it connect to your regtest network.