Event JSON
{
"id": "11d6372a4bc62456e67ed19d3da9d8049ea660f825bb3e504cdfd4d69878a0e3",
"pubkey": "e2758e166e0556cc0d19edd264ab6628420acccdfb52a575f6ddd7cb79a056e4",
"created_at": 1739185700,
"kind": 1,
"tags": [
[
"p",
"fcd3e56e10427fbb3a665ce9ff0dff1165efcf1c14b47820f8b9d8a88398cb8f",
"wss://relay.mostr.pub"
],
[
"p",
"9b62738b9c58709839f1c484a97cf4eea9198689eebd7b4c0ecd5060c31b405a",
"wss://relay.mostr.pub"
],
[
"e",
"ff47f48117a4898013c2b5ae2f1fc06381973e87b8ceed939843601fc4ae1c28",
"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/113979274080393165",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlnf72mssgflmkwnxtn5l7r0lz9j7lncuzj68sg8ch8v23qucew8s4hfvmu I think I didn't explain well, because that wasn't my intention: I think when creating CNs you should have a similar interface with recommendations based on what other people use.\n\nYou can then build both sensitivity markers and filters based on that.\n\nCrucially, CNs should be treated independently from marking something as sensitive, because the latter is very much dependent on the reader. I wouldn't consider NSFW sensitive, others – rightly so – do. And right now the user experience for CNs is crap because clients consider everything with a CN as sensitive.",
"sig": "9109f1bb89aac6504974a1da1cd25e80f8f1446a8836152f28a707827ddaf6b92fa215023464f6fb16cd0613e49c271aa27d67062d679c6ea3c500b6c4345d47"
}