@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.
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.
@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.
No replies yet.