a knob that adjusts this setting won't stop the tx from getting into your node, but alright. you keep telling yourself that.
Discussion
It doesn’t stop all, but it does stop most, like how all filters (email spam etc) work.
simply not true.
your node will then start relaying this CSAM to other nodes after it comes in a block, I don't see the point of a knob that does nothing except delay for 10 minutes.
this is still true even with 99.999% knots usage. people relaying this stuff won't be doing it through knots nodes.
There’s a difference between what ends up on the timechain and what I choose to accept in my mempool.
And with Core v30 lifting OP_RETURN limits to nearly 4 MB (a 50,000× increase) the risk of vast CSAM being permanently embedded becomes a much bigger issue.
what appears in your personal mempool has no impact on what will be accepted in a block.
My node alone won’t. But enough Knots runners and aligned miners (eg. Ocean) can shape what propagates. You choose defeatism. I do not.
Why isn't it there already then? Please don't say that it isalready there because someone chunked something up to look like utxos and spread it out across lots of transactions. If filters don't do anything why don't we already have big long strings of CSAM in the op return field? Don't say its because no one wants to upload it, someone already went through all the trouble of chunking it up to look like normal monetary transactions.
Why do they need to remove the knob though?
This is all retarded and I don’t trust anyone. One side has a bunch of shitcoiners and the other is a bunch of religious nuts…
because it doesn't do anything useful. mempool settings are incredibly niche for non-mining nodes, unless you are optimizing memory, but then you would just use the total mempool size setting.
I've been running a node since 2010 and I never once needed to tweak this, only ever mempool memory usage.
non-useful code is dead code and is a maintenance burden. non-useful code is also confusing to users who think tweaking the knob will actually do something.
Sorry but I don’t buy that excuse…
How much additional maintenance does allowing users flexibility to update settings on their node really require?
Just seems very suspect that this is the hill core devs are deciding to die on.