My side? Again I’m not in a cult. I don’t have a side. I do recognize that you will never stop spam, and that filters create more issues than they solve and push spam into worse areas of the system.
You are also ignoring over a decade of cyberpunk knowledge around open decentralized protocols and how the legal system deals with them. As soon as you create a system where node operators can absolutely control what makes it onto the network the expectation by the state will be that you will comply with their demands. You tread a dangerous path on your righteous crusade.
Login to reply
Replies (2)
Compromised Core devs deliberately allowed inscription spam, retard.
See the compromised Core devs who rejected Luke's PR that fixes inscription spam. They are the bad actors (the NACKers)
They revealed themselves with their public comments on OP_RETRUN being dishonest and manipulative.
The guys that ACKed are the good guys we have.
https://github.com/bitcoin/bitcoin/pull/28408
https://github.com/bitcoin/bitcoin/issues/29187
Bitcoin Knots has fixed those issues.
View quoted note →
https://github.com/bitcoin/bitcoin/pull/28408
https://github.com/bitcoin/bitcoin/issues/29187
Bitcoin Knots has fixed those issues.As node runners we intend to preserve Bitcoin's primary usecase (money, not JPGs, not "data").
The current spam is obfuscated and fragmented (and Core is responsible for much of it by REFUSING to fix Inscriptions exploit bug).
100k OP_RETURN will allow for high fidelity CSAM images in an inmutable blockchain. We did not sign up for that crap, so forgive me if we are playing defense here by trying to preserve Bitcoin.