mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-12-09 16:48:50 +00:00
Compare commits
2 Commits
no-batchin
...
communitie
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
7bac93607f | ||
|
|
2f403e1e95 |
19
72.md
19
72.md
@@ -14,7 +14,6 @@ The goal of this NIP is to create moderator-approved public communities around a
|
|||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
"created_at": <Unix timestamp in seconds>,
|
|
||||||
"kind": 34550,
|
"kind": 34550,
|
||||||
"tags": [
|
"tags": [
|
||||||
["d", "<community-d-identifier>"],
|
["d", "<community-d-identifier>"],
|
||||||
@@ -40,11 +39,23 @@ The goal of this NIP is to create moderator-approved public communities around a
|
|||||||
|
|
||||||
# New Post Request
|
# New Post Request
|
||||||
|
|
||||||
Any Nostr event can be submitted to a community by anyone for approval. Clients MUST add the community's `a` tag to the new post event in order to be presented for the moderator's approval.
|
A "post request" is an event that can be published by anyone with the intention to be displayed inside a community. Moderators will be notified of this request and decide about approving it or not. Only after approval these posts will be displayed inside the communities.
|
||||||
|
|
||||||
|
Event kinds defined in other NIPs can be supported inside communities, but here we defined kind translations for them such that they don't get confused with events published outside communities.
|
||||||
|
|
||||||
|
| Community-scoped Kind | Description | Original Kind | Original NIP |
|
||||||
|
| --- | --- | --- | --- |
|
||||||
|
| 11 | Community post | 1 | 1 |
|
||||||
|
| 10500 | Community-scoped user metadata | 0 | 1 |
|
||||||
|
| 10501 | Community-scoped follow list | 3 | 2 |
|
||||||
|
| 4548 | Community file metadata | 1063 | 94 |
|
||||||
|
| 30500 | Community long-form article | 23 | 23 |
|
||||||
|
|
||||||
|
So, for example, in order to publish a "text note" (`kind:1`) inside a community one must use the `kind:11` instead.
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
"kind": 1,
|
"kind": 11,
|
||||||
"tags": [
|
"tags": [
|
||||||
["a", "34550:<community event author pubkey>:<community-d-identifier>", "<optional-relay-url>"],
|
["a", "34550:<community event author pubkey>:<community-d-identifier>", "<optional-relay-url>"],
|
||||||
],
|
],
|
||||||
@@ -53,8 +64,6 @@ Any Nostr event can be submitted to a community by anyone for approval. Clients
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
Community management clients MAY filter all mentions to a given `kind:34550` event and request moderators to approve each submission. Moderators MAY delete his/her approval of a post at any time using event deletions (See [NIP-09](09.md)).
|
|
||||||
|
|
||||||
# Post Approval by moderators
|
# Post Approval by moderators
|
||||||
|
|
||||||
The post-approval event MUST include `a` tags of the communities the moderator is posting into (one or more), the `e` tag of the post and `p` tag of the author of the post (for approval notifications). The event SHOULD also include the stringified `post request` event inside the `.content` ([NIP-18-style](18.md)) and a `k` tag with the original post's event kind to allow filtering of approved posts by kind.
|
The post-approval event MUST include `a` tags of the communities the moderator is posting into (one or more), the `e` tag of the post and `p` tag of the author of the post (for approval notifications). The event SHOULD also include the stringified `post request` event inside the `.content` ([NIP-18-style](18.md)) and a `k` tag with the original post's event kind to allow filtering of approved posts by kind.
|
||||||
|
|||||||
Reference in New Issue
Block a user