I’m not talking about optional levels of engagement. if that were the discussion, i wouldn’t be engaging in this conversation. My concern is purely about illegal content, and how that could be used by the censorship industrial complex to trojan horse nostr. The best way to mitigate that is to come up with a system that handles that problem without offering the Feds an attack surface they can use in other ways. Which is no small feat.

It just dawned on me that keeping media delivery separate is the key. clients could incorporate external media delivery services like nostr.build, and those services would bear the brunt of dealing with illegal content. If people then used external links to bypass media delivery systems, this is something outside of the control of nostr, and outside of client developers responsibility. That is the purview of the Feds. If then, a media delivery service got weird and started censoring for reasons outside of illegality, they could be replaced, or bypassed by posting external links, preventing full centralized censorship. If a client starts moving past this, and centralizes censorship for arbitrary reasons, they can be replaced.