I spent the weekend rethinking "NIP-69" that Rabble (npub1wmr…g240) and I had proposed. Based on some of the comments we had gottten I started with the idea of "labeling" and made the data needed for #ContentModeration just another type of labeling data.
That required coming up with a NIP for doing labeling. I made it so you can use _any_ coding system / defined vocabulary. Do you want to tag your posts (or someone else's) with some ISO code, or a GeoNames place ID, or some code from a structured vocabulary like MeSH? Or maybe you have your own defined vocabulary (like I do)… You can do that with what I'm calling "NIP-68". You can see it here…
https://github.com/s3x-jay/nostr-nips/blob/master/68.md
I'm hoping that NIP makes Nostr interesting to the scientific community. (It would be very funny if "the gay porn guy" kicked off the process of getting scientists onto Nostr.)
Then… I reworked our NIP-69 proposal so it's just a defined vocabulary for NIP-68 labeling. Actually it's two defined vocabularies. One is somewhat rigid, the other is more organic - anyone can just create a new moderation-related code and start using it. You can see my new NIP-69 here…
https://github.com/s3x-jay/nostr-nips/blob/master/69.md
It does have an impact on how things are done now. It deprecates both NIP-36 and NIP-56 and requires paid relays to accept moderation reports from unpaid users if the content being reported is on the relay. (Without that change relay owners may never know they have illegal content on their relay).
Client apps can keep their current "report post" UI (or enhance it with new features), but they will need to change the event that's sent from type 1984 to type 32123. The few apps that are using the reports to filter/block what their users see (like Vitor Pamplona (npub1gcx…nj5z)'s Amethyst) may need to make more more substantial changes (but they may want to wait, since this isn't the end of the suggestions regarding content moderation).
I'm still discussing with Rabble the best way to present 68 & the new 69 as Nostr PRs, but that will probably get done in the next day or two.
s3x_JAY / s3x_jay
npub1vee…38wt
2023-05-01 14:58:13
Author Public Key
npub1veeqt66jt2j209y9nv4a90w3dej074lavqygq5q0c57dharkgw0qk738wtPublished at
2023-05-01 14:58:13Event JSON
{
"id": "5fe5eb146cd32bf481428cfc669bed57804f8e5c29a375f4bb43399c863ac781",
"pubkey": "667205eb525aa4a794859b2bd2bdd16e64ff57fd600880500fc53cdbf476439e",
"created_at": 1682945893,
"kind": 1,
"tags": [
[
"p",
"76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa",
"",
"mention"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"",
"mention"
],
[
"t",
"ContentModeration"
]
],
"content": "I spent the weekend rethinking \"NIP-69\" that nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 and I had proposed. Based on some of the comments we had gottten I started with the idea of \"labeling\" and made the data needed for #ContentModeration just another type of labeling data. \n\nThat required coming up with a NIP for doing labeling. I made it so you can use _any_ coding system / defined vocabulary. Do you want to tag your posts (or someone else's) with some ISO code, or a GeoNames place ID, or some code from a structured vocabulary like MeSH? Or maybe you have your own defined vocabulary (like I do)… You can do that with what I'm calling \"NIP-68\". You can see it here…\n\nhttps://github.com/s3x-jay/nostr-nips/blob/master/68.md\n\nI'm hoping that NIP makes Nostr interesting to the scientific community. (It would be very funny if \"the gay porn guy\" kicked off the process of getting scientists onto Nostr.)\n\nThen… I reworked our NIP-69 proposal so it's just a defined vocabulary for NIP-68 labeling. Actually it's two defined vocabularies. One is somewhat rigid, the other is more organic - anyone can just create a new moderation-related code and start using it. You can see my new NIP-69 here…\n\nhttps://github.com/s3x-jay/nostr-nips/blob/master/69.md\n\nIt does have an impact on how things are done now. It deprecates both NIP-36 and NIP-56 and requires paid relays to accept moderation reports from unpaid users if the content being reported is on the relay. (Without that change relay owners may never know they have illegal content on their relay). \n\nClient apps can keep their current \"report post\" UI (or enhance it with new features), but they will need to change the event that's sent from type 1984 to type 32123. The few apps that are using the reports to filter/block what their users see (like nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z's Amethyst) may need to make more more substantial changes (but they may want to wait, since this isn't the end of the suggestions regarding content moderation). \n\nI'm still discussing with Rabble the best way to present 68 \u0026 the new 69 as Nostr PRs, but that will probably get done in the next day or two. ",
"sig": "4c764d6915837391cab048047bae31655df387e37783d73e53ce47e2954dc9ee48226085e2bd6dd4cd63c61d6de8f4ca842c6fc16c81b75483f5954138ee7b05"
}