yes, but THAT IS WHY :-) any group that develops a client (such as core), should engage with the community to ensure everyone is onboard with specific changes. Obviously not every change will cause a significant amount of the community to start running a fork. Core obviously has more history and more funding and I'm not even a fan of luke, but it is not personal or about who. It is about what and the arguments.
I really dont know or dont care much about who in particular the developers are.
It's not and never was about
- staunch defenders
- or the bad guys
"Filters dont work" has been debunked. They do work. If they didnt, then why remove them? Bitcoin was just fine for the past decade without removing them.
You also havent answers to why you think removing them would help with decentralization - it seems the opposite will happen once BTC will be targeted by CSAM just like BSV was and less noder runners would want to be involved with it and only big players can and will filter those kind of transactions from their mempool, essentially causing centralization.
If you don't agree with that argument, you should be able to argue for why this is not a risk and also why removing filters will presumably help with more decentralization.
Login to reply
Replies (1)
Core should not engage with community, thats not really possible. The community is the entire world. How exactly would you derive signal from that?
Community should get involved in dev, its the only way this works