What? You can set policy however you want to in core? WTF are you talking about. Every node, no matter what flavor, further decentralizes the network...
You are really confused my guy.
What? You can set policy however you want to in core? WTF are you talking about. Every node, no matter what flavor, further decentralizes the network...
You are really confused my guy.
Default settings are important, thats why core wanted to remove the ability to change them. I thought you were in favour of decentralisation?
firstly, They DIDN'T remove them. The default limit was changed to like a million bytes or something. Basically no limit. You can still set a limit just fine with core. Even when 30 comes out.
secondly, if and when they DO remove OP_RETUN limit it's just the OP_Return limit. All other policies remain. policies generally exist to make sure the user doesn't fuck something up and make a bad tx. It's not for making sure the network doesn't get the transactions.
I actually don't run core or knots, but I do run a node. I'll let you guess the flavor. It's one that doesn't have any policy restrictions for anything. I can make whatever transaction I want to with my node.
So you need to run a node without filters to spam Bitcoin. Understood. 
I don't spam Bitcoin.
Then stick within 80 limit 
Not my node. I want an accurate picture of the mempool when I make a regular transaction.
Majority of noderunners disagree with you. So you won't have an accurate men pool.