No, your framing is dishonest.
Respectively, each scenario is:
- no CSAM: no jail
- no CSAM: no jail
- no CSAM: no jail
- CSAM: jail
Thread
Login to reply
Replies (2)
I’ve heard you say before there can be no CSAM in Inscriptions because CSAM in Inscriptions can only be “misinterpreted” as CSAM.
I doubt many people would agree with this… but let’s park that.
How is 101kb of CSAM in OP_RETURN not CSAM??
Question from someone who's not up to speed on all of the technical details and arguments, but believes that enabling 100kb OP_RETURN is begging for legal problems:
Is it technically possible to develop a compromise solution that gives the "shitcoiners" (projects that want better hooks for integration and new capabilities) what they want without providing an ideal storage space for illegal files?
IMO, inscriptions etc. are nonsense and should be eliminated, if possible, but I can see the utility in improving trustless integration with ancillary systems.
The middle path > ideological purity (IMO)