It would be nice to get it implemented more widely. I'm more than happy to flag my spicy content to keep it off of the streams of people that don't want to see it.
nostr:npub1kmsnnxw6p8vlk2l2dh0443jkj0txl7jrww8qpx4vd428he0a8jqqy6tjep It turns out there is a content warning specification in the nostr protocol (NIP-36). The Snort.social web client uses it, but support in other clients is limited for now.
It would be nice to get it implemented more widely. I'm more than happy to flag my spicy content to keep it off of the streams of people that don't want to see it.
No replies yet.