s3x_SOCIAL on Nostr: Thanks for asking (seriously). I'm not a lawyer, but having been in the adult ...
Thanks for asking (seriously). I'm not a lawyer, but having been in the adult industry for ~15 years I've learned a thing or two…
The problem is if you're hosting adult content (images/videos, it's not really an issue with text) you need proof of consent and proof of age (plus the proof ownership or license to use that you need for all content). The site doesn't always have to have proof of consent / age on file, but it does need to confirm that they exist.
For example - take a photo of someone else on a beach and upload it to the Internet - no problem - it's a public place and there's no expectation of privacy. Do the same thing on a nude beach and you need proof of age and proof of consent.
The moment you host something without at least a nominal check of age and consent you open yourself up to all sorts of problems. The laws on CSAM and things like revenge porn are really strict and the penalties are often harsh. Big corporations get away with more because they have teams of lawyers. But a single significant legal incident can put a small company out of business.
I've got over a million unique images in my porn database at the moment (and probably another 600K or so I need to import). It's terabytes of data. And if I've learned one thing dealing with those is you don't store images/videos in databases - you store them externally.
nothenry (npub1xv6…xea6) had suggested an approach where there was a more traditional POST to submit the image/video. That's something I could consider. But then it gets to your interface question - I'd need some sort of confirmation of:
- ownership/license
- consent
- age
But it's one thing when someone confirms those things on my site, but it's another thing for me to trust a 3rd party to confirm those things. Maybe… But I'd have to think about it some more.
But at the end of the day storing images/videos in the relay database is a non-starter for me even with all the documents in the world. I know better than to do that. Which is why I love NIP-94, but not NIP-95.
The problem is if you're hosting adult content (images/videos, it's not really an issue with text) you need proof of consent and proof of age (plus the proof ownership or license to use that you need for all content). The site doesn't always have to have proof of consent / age on file, but it does need to confirm that they exist.
For example - take a photo of someone else on a beach and upload it to the Internet - no problem - it's a public place and there's no expectation of privacy. Do the same thing on a nude beach and you need proof of age and proof of consent.
The moment you host something without at least a nominal check of age and consent you open yourself up to all sorts of problems. The laws on CSAM and things like revenge porn are really strict and the penalties are often harsh. Big corporations get away with more because they have teams of lawyers. But a single significant legal incident can put a small company out of business.
I've got over a million unique images in my porn database at the moment (and probably another 600K or so I need to import). It's terabytes of data. And if I've learned one thing dealing with those is you don't store images/videos in databases - you store them externally.
nothenry (npub1xv6…xea6) had suggested an approach where there was a more traditional POST to submit the image/video. That's something I could consider. But then it gets to your interface question - I'd need some sort of confirmation of:
- ownership/license
- consent
- age
But it's one thing when someone confirms those things on my site, but it's another thing for me to trust a 3rd party to confirm those things. Maybe… But I'd have to think about it some more.
But at the end of the day storing images/videos in the relay database is a non-starter for me even with all the documents in the world. I know better than to do that. Which is why I love NIP-94, but not NIP-95.