Who said the nodes can't decide? What you're advocating for is not in the nodes' best interests.
But am I biased: I run an rpi node
Discussion
Core says the nodes cannot decide. they removed the option.
Exactly. Let nodes configure as they wish, as they historically have been able to.
That's an entitled view. How else should core allow nodes to misconfigure themselves? Nodes are welcome to run whatever code they like, just as Core is allowed to write whatever they like.
That's a separate issue from what I had said, which is that adding filters beyond consensus to mempool doesn't accomplish the stated goals, and is ultimately harmful to node operators
You asked the question, "Who said the nodes can't decide?" I answered you with the fact that Core turned off filters and removed the option to turn them on.
Therefore, Core says nodes cannot decide. Clear and simple.
Clearly he’s one of the gaslighters.
Throwing mud doesn't make your arguments any better. Mempool filters reduce memory usage, but have no effect on block sizes. Only changes to consensus can do that
So?
Mempool is small compared to the chain. Small nodes aren't running out of memory, they're running out of disk space
This has nothing to do with the reasons why aggressive filtering should be the norm.
If it isn't the mempool size, and it isn't the chain size, presumably it's censorship. But if you'd like to actually say what you're alluding to that would be easier than me guessing
lol if you’re locking your front door, then that’s censorship too
Limiting OP_RETURN is as effective as locking your door and leaving the windows open
Actually, it’s effective as locking the door and closing all the windows too. A motivated thief will still find a way to break into the house but most people will simply not try to enter.
Watch Mechanic on the What Bitcoin Did podcast. He perfectly explains the contradictions the spammers hold on to without knowing.