By definition, in #Bitcoin, a node's job is NOT to dictate what kind of transactions should go in the blocks. Their job is to ensure that the rules are being followed on the network, transactions and blocks are valid and coordinate the work of miners.

If that is true then I don't consent to run your definition of Bitcoin.

You really are lost.

If you end up forking yourself out of consensus later down the line with the decisions you make in favor of distancing yourself as much as possible from personal responsibility and yielding more power to dishonest technocrats, you can go crying to Papa Lopp, because you'll only get an "I told you so" from me.

If you don't have control over your mempool, who the fuck do you think does? If everyone thought like you, they'd surrender to a dictatorship of developers dumbass.

Sorry, the level of willful ignorance is just baffling.

Miners dont even have to be *convicted* bitcoiners. They could even be fiat maxis trying to profit off of a low cost energy source - immediatety converting corn to fiat trash. That is one of the marvels of POW consensus and coin emission (DA-POW), it is fueled by greed and opportunity, not those looking to "support their project"

If you run example knots or core you run it 😄

Clarify which dictatorship you want. Because if it's not dictatorship of me over only my mempool and nobody else's, then as a matter of fact I am not running your idea of Bitcoin. I have control over my node. I have a mind and I use it to tailor my settings. What you want is a dictatorship of developers, ironically, just your preferred flavor of it.

Everyone running a node has control over their mempool. Some node runner wants to see the whole picture and all available valid transactions so they can clearly see what's going on in the network, some wants to filter some transactions out and see the network only partly and some want to see only specific transactions in the mempool. One noteworthy thing I noticed when playing with the filters was that, we have to download twice the transactions we try to filter. Once when we see them first time and reject it and second time when they enter in the block. It's not that bad but if one wants to optimize bandwidth usage they should not use any filters.

Have you looked into the cache settings?

You have control over your node but not over what valid transactions are included in the blocks, except if you work and mine them by yourself. Mempools can be full of various transactions but only transactions that pay enough fee to be included in block are relevant in the end. I want developers to not dictate anything about transaction types. Bitcoin transaction is a digital message and I want everybody to be free to sign any kind of message they want as a transaction even if I and 99% of other users consider it spam/waste. We know that free market is the only way to filter transactions without dictatorship and I would like to have as many people as possible to understand that so we can continue with more productive discussions like Bitcoin privacy and censorship resistance.

I didn't know that there's a way to use mempool cache to also include filtered transactions, but I guess that makes sense if using filters. Thanks for the notice.