Here is my understanding of the ongoing controversies around the nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze saga. I think there is a lot of generalizations and misunderstandings happening. I'll ELI5 the situation as I understand it. Please correct me if any of my facts are wrong. My opinions are my own, dont correct those. I can amend those myself.

Ocean is not specifically targeting coinjoins. It is only samurai implementation that is being affected (and I believe unintentionally).

I believe ocean is intentionally targeting inscriptions, yes. To be clear, I do not agree with what they are doing but I also do not believe they are out of bounds.

Miners are free to set parameters on their node. This is not controversial. Ocean is setting the upper threshold for data size to a lower parameter than what is the current norm in order to bulk filter out inscriptions.

As a side note, it's my opinion that suppressing oceans right to set parameters and filter out the blocks they feel to be spam is an act of centralization in trying to force Ocean to follow the current status quo. Ocean is well within their rights to construct block templates however they see fit. Their ability to mine that template is the checks and balances that decentralization offers.

The unintended result is also filtering out samurai coinjoin transactions. To be clear, other coinjoins are still fine.

And finally, exactly zero blocks have been mined by Ocean since knots was implemented. So their impact has been exactly zero. 

If you don't like what they are doing, you're free to point your hashrate elsewhere. Ocean is free to construct their block templates however they wish. That is their right as a miner. It will be to no avail if they dont have hashrate behind them. Just like on nostr you're free to mute spammers, Ocean is free to set their parameters to exclude what they feel to be spam on the blockchain. If you disagree, simply move your hash and everything they are doing is moot. It's that easy.

THE SYSTEM IS WORKING EXACTLY AS INTENDED