Thanks for the link to the other comment. Very instructive and much better explained than what I could have.

south_korea_ln

Still, it looks to me like much ado about nothing.

Rather than burying their head in the sand and avoiding facing this reality, several core developers agree that it might be better to just remove the restrictions. This won't remove the shitty behavior, might even make it easier to do some of the shitty behavior, but it'll happen without all the tricky stuff the Bitcoin shitcoiners had to resort to to achieve their shit.

Why do you think the core devs feel this way?  My understanding is right know its an option each node can set  to opreturn byte limit themselves so removing the option seems worse than giving each noderunner a choice.

edit:  heres a good answer to my question in another comment: 

AskSN

Can Someone Please Tell Me What is Going On With Bitcoin Core

Cje95

> Still, it looks to me like much ado about nothing.

Agreed.

>Rather than burying their head in the sand and avoiding facing this reality, several core developers agree that it might be better to just remove the restrictions. This won't remove the shitty behavior, might even make it easier to do some of the shitty behavior, but it'll happen without all the tricky stuff the Bitcoin shitcoiners had to resort to to achieve their shit.

Why do you think the core devs feel this way?  My understanding is right know its an option each node can set  to opreturn byte limit themselves so removing the option seems worse than giving each noderunner a choice.

edit:  heres a good answer to my question in another comment: https://stacker.news/items/968321/r/ChrisS?commentId=968369