Profile: ca08029a...
Here's one possible approach: nostr:nevent1qqsp0l92vytmzeq03k3sqd0hyldv9utg8t9wgk0yffj7njalm45qzgcpzfmhxue69uhhqatjwpkx2urpvuhx2ucpkp9n5
Agreed, the protocol should not concern itself with this stuff. However, clients and relays must.
The really nasty thing is that it's also illegal in the US to report child porn to anyone other than NCMEC. This problem has to be solved not only for nostr's reputation, but also because it puts everyone at risk (especially amateur relay operators).
No, I'm only here to continue the conversation already started and be a resource for devs trying to figure out what to do with illegal content.
It seems like many of them don't know what sort of risks they're exposing users to by creating "reporting" features. Others, like nostr.build are doing the right thing by reporting stuff to NCMEC.
Coordination between service providers is challenging, which is good for censorship resistance, bad for keeping users safe from legal liability.
I've adopted the term "Trust and Safety" as my username with tongue somewhat in cheek, sort of like our revered "Nostr CEO".
A very promising organization for helping decentralized service providers deal with illegal content: