Can you elaborate? Trying to gather intel

why would people who have been staunch defenders of decentralization all of a sudden be the bad guys? is your cognitive dissonance so strong that you can’t recognize you are being fed a false narrative? filter don’t work, they just want influence so they can make unilateral changes to bitcoin. Wake up.

How so ?

Yeah, unlimited OP_RETURN was always enabled and datacarriersize has always been a deprecated feature of bitcoin That's why people are just seeing it now 🙄

So what @jb55 ? Why are you so concerned about us poor stupid knots nodes? Are you trying to save us from %gasp% underpaying a fee? 🤯

Yes, by Core groupies and professional gaslighters. Filters work, even devs have admitted that already. That’s why you fail to understand the rise of Knots. View quoted note →

Just a reminder that bad actors come into movements all the time to try and subvert or degrade the movement. Happens to all movements. (occupy wallstreet, black lives matter, bitcoin, religion, etc) Any group could TRY to subvert bitcoin or subvert the other group. So be careful to not to think your team could do no wrong. I think it's dumb to think that current knots users would just go along with anything knots did. They just turned on cores idea, why wouldnt they turn on knots if they starting doing something that didn't align with their values? I'd be interested to hear what you think knots would do that could somehow subvert bitcoin from being decentralized. At this point knots is just mainly just reimplementing existing things, not exactly crazy since we're still running a lot of the same rules currently on most nodes. Just because there is a window open that allows spam, but in a bad way (UTXO bloat). Doesn't mean we should open the front door to "solve" one problem and very likely introduce another. (Aka it doesn't solve the actual technical problem, just incentivizes spammers to use the front door) Maybe we screwed up and the initial "bug" that allows the problem needs to be patched. If there was a bug that let me put my movie files on a server meant for medical information, and my files could never be deleted, it would be patched ASAP. The biggest issue, as I see it, is the larger data limit or potentially no limit. It makes for poor incentives.

Let nodes decide what filters to set or not set. Knots allows this. Core, like the nanny state, does not.