nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Vitor, this would def be nice.
Discussion
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.
@florian | Photographer The #plebstr dev saw a post I did to see how different clients handled NIP-36 and said he'd get it implemented in the next update. I love it here.
👍 You can test on my profile too. Have several created with snort.social
Happy to see it in TestFlight already today! Works as expected for the posts … maybe a setting to generally disable the warning would be good for people who want to see everything.
That’s the fastest turn around I’ve seen from a stated want in a network to testing. Light speed devs over here
nostr:npub1eqmj85el4pkg7qdj2jcae24qykev5evnyz2s6pzdytzpkhga4u5sdmhexk found a UX issue with the content warning … when you have revealed the post and then click on the post to open the detail view the content ist hidden again.
I would expect the content in the detail view still being revealed.
Good point, i will fix that
We already implement sensitive content.