nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlnf72mssgflmkwnxtn5l7r0lz9j7lncuzj68sg8ch8v23qucew8s4hfvmu (nprofile…fvmu) Absolutely! I think part of the issue is the messaging and the UX around CWs unfortunately. Clients consider CW'ed content as "more sensitive" rather than just tagged. Indeed, arguably the opposite should be the case, content that has no CW should be considered sensitive because there's no way to know what's "in there". A client may also consider certain CWs, such as nsfw/lewd and/or gore as sensitive by default, with user being allowed to add/remove those sensitivity markers (or downright filter/remove them).
For authoring messages, I think CNs as a tumblr-style tagging would also improve the situation a lot: Tags are auto-completed based on who already used that tag (but you can create as many as you like in any form), and usually, the better you tag, the better you find stuff. Also it's easy and common to re-blog while adding more tags. In addition, CNs/tags shouldn't be hidden behind a button, but part of the standard authoring process.
Right now, it is burden of the author to mark something as sensitive and the reader is at their mercy. Rather, it should be the authors job to tag things as accurately as possible and the reader can then configure which topics are sensitive, to them.
Leonard/Janis Robert König /
npub1uf…m774h
2025-02-10 10:24:49
in reply to nevent1q…nres
Author Public Key
npub1uf6cu9nwq4tvcrgeahfxf2mx9ppq4nxdldf22a0kmhtuk7dq2mjqmm774hPublished at
2025-02-10 10:24:49Event JSON
{
"id": "d282acfae1196dcb21488d4aa42e698b4921ec029101228de1ea1c1ac02ab118",
"pubkey": "e2758e166e0556cc0d19edd264ab6628420acccdfb52a575f6ddd7cb79a056e4",
"created_at": 1739183089,
"kind": 1,
"tags": [
[
"p",
"fcd3e56e10427fbb3a665ce9ff0dff1165efcf1c14b47820f8b9d8a88398cb8f",
"wss://relay.mostr.pub"
],
[
"p",
"9b62738b9c58709839f1c484a97cf4eea9198689eebd7b4c0ecd5060c31b405a",
"wss://relay.mostr.pub"
],
[
"e",
"1de7dfbd132fdeb1bea34fcbe997fd90b848f45cf932e11a2f37b1051ad7ecc2",
"wss://relay.mostr.pub",
"reply"
],
[
"content-warning",
"Meta, The thing with the CWs an politics, flooding the zone with shit 🧵"
],
[
"proxy",
"https://todon.eu/users/ljrk/statuses/113979102969839829",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlnf72mssgflmkwnxtn5l7r0lz9j7lncuzj68sg8ch8v23qucew8s4hfvmu Absolutely! I think part of the issue is the messaging and the UX around CWs unfortunately. Clients consider CW'ed content as \"more sensitive\" rather than just tagged. Indeed, arguably the opposite should be the case, content that has no CW should be considered sensitive because there's no way to know what's \"in there\". A client may also consider certain CWs, such as nsfw/lewd and/or gore as sensitive by default, with user being allowed to add/remove those sensitivity markers (or downright filter/remove them).\n\nFor authoring messages, I think CNs as a tumblr-style tagging would also improve the situation a lot: Tags are auto-completed based on who already used that tag (but you can create as many as you like in any form), and usually, the better you tag, the better you find stuff. Also it's easy and common to re-blog while adding more tags. In addition, CNs/tags shouldn't be hidden behind a button, but part of the standard authoring process.\n\nRight now, it is burden of the author to mark something as sensitive and the reader is at their mercy. Rather, it should be the authors job to tag things as accurately as possible and the reader can then configure which topics are sensitive, to them.",
"sig": "3f84860fb64c180995f193f774f037b384b28b8fb84bee3d7e4610bc87d3256af336ca805d6f7eb3e112c07b433d04f1c8f45268e4af0744a37710d29b3297c1"
}