I didn't express my own opinion. I was asking yours. But since sorta ask (in that backhanded way), I'm able to simultaneously BOTH 1) want to conveniently be able to adjust policy on my node and 2) recognize spam propagation is a larger program that user-level filters dont adequately solve. and yeah one of my nodes has been Knots for a couple years. it doesn't filter Whirlpool CJ txs from its mempool. and the vast number of users will run defaults or apply filter parameters blindly from a centralized platform. you pretending like that isn't true doesn't help anybody.