Look at how OnlyFans models work currently. Their protected content goes on the OF website. But all their promos go in the general feeds of Twitter, Instagram, etc. I’m not saying there won’t be use cases where the adult industry uses something other than Kind 0, but they will need to use Kind 0 on a regular basis.
Discussion
Sorry - had a brain fart there. I meant Kind 1, not Kind 0.
Sure. That’s my point. Kind1 is general use short message content. It’s not paywalls, galleries, long form movies, live video chat, a chat room, etc.
If you want to funnel specific use content, perhaps with paywalls and other aspects, use a different kind.
Or, as I suggested, host a purpose specific relay for the content. People opt-in then by enabling that relay - even for kind1.
They 99% of population do not want explicit and general content mixed. You can try, but I expect it will fail spectacularly and will result in endless reporting or user bans from relays.
Another idea you could suggest is a relay metadata flag for explicit content - then clients can know connecting to that relay is going to expose clients to that kind of content.
I’ve suggested a lot of ideas for you. All are valid for the network to support in the long term, and are solid an alternative to some formal content rating system.
I still don’t understand your proposed problem statement or desired outcome - except flood kind 1 today with mixed general and explicit content because you think it has to be in a single stream - and that makes no sense.
And to clarify.. they can use kind 1 for general content (non-explicit profile picture, non-explicit banner, likely toned down profile, etc). But as soon as it becomes offensive and blasts unwanted content into general feeds - it will be a problem. We’ve had porn blasted in general feeds and people hated it… people even stopped using Nostr altogether.
Maybe they should have two accounts. One for general use posts, and one for explicit. Or just use one, but have toned down imagery. And only post explicit content to targeted relays. Problem mostly solved.
Nostr is a Protocol to support many use cases… not a dump everything in kind 1 because I think I need to. If people care enough, apps will add support for kind 69 or whatever you propose.