Wouldn't it make more sense to do this at the relay level? So for example when you install a Nostr client it doesn't have nsfw relays by default, so no one sees it unexpectedly and it doesn't violate App Store and Play Store policies, but add them manually and you can access nsfw content, mark a post nsfw and it's only sent to the nsfw relays.

This could be done with a new event type relays would ignore by default but admins can enable in the config.

Reply to this note

Please Login to reply.

Discussion

There is an adult only relay out there already - adult.18Plus.social - their intent was to just have adult content. But if you look at what's on it - it's got all sorts of stuff, not just adult content.

I'm working on getting up a adult/LGBT-friendly relay as well. But I never envisioned it as something that had even a majority of adult content. The new age verification laws in places like Louisiana exempt sites with less than 1/3rd adult content. I expect to fit within that criteria (if it applies to my relay - I think the law only applies to "sites" - not their data providers).

Also, define "adult"… The definition of adult in Sweden is different than in Saudi Arabia. You can't say "all adult content goes over here" - because "adult" is a social construct and Nostr is something that can't be based on one culture's norms.

All valid points. I was thinking from a purely technical perspective as cultural norms and varying laws are way more complex issues. That's also why I use the term nsfw rather than "adult" since it's much more easily quantifiable - anything you wouldn't want your boss to see over your shoulder.

But even on a technical level, anything that relies on the honour system is gonna be abused, so you got me there.

This is a tricky one because any method relying on the user to classify their own content as nsfw or not suffers from the same weakness.