it doesn’t make it easier, it just changes core to reflect reality. People making these kinds of custom transactions are not relaying via core. I don’t see why doing it with bitcoin-cli is any easier than a web form submission. Most people building protocols that depend on this would not be using core relay anyways, they would just go around it

Op_return limit from 80bytes to 100kb doesn't make it easier? Why do it at all?

You're not filtering jack unless you implement and enforce stricter consensus rules. Your Knots node will store and serve data you detest once it gets confirmed in a block.

So, you are saying Bitcoin is captured and states can go after node runners for hosting and distributing cp they never wanted because we have no tools to filter this stuff out, no matter which distribution we run? Hey hey congrats on that.

My mempool is my responsibility. Confirmed transactions are the miner's responsability. I can't be held responsible for other people's actions, but that doesn't mean I shouldn't act morally. Also, confirmed and unconfirmed transactions are completely different.

If you wish to make such assertions, I suggest you get an actual practicing attorney to publish an opinion to that effect. Good luck!

Feel free to employ whatever pretzel logic helps you cope better 🤷🏼‍♂️

To make p2p relay network work better and thus keep tx relay decentralised.