support for community-exclusive posts

72.md

@@ -4,9 +4,9 @@ NIP-72
 Moderated Communities (Reddit Style)
 ------------------------------------
 
-`draft` `optional` `author:vitorpamplona` `author:arthurfranca`
+`draft` `optional` `author:vitorpamplona` `author:arthurfranca` `author:vivganes`
 
-The goal of this NIP is to create moderator-approved public communities around a topic. It defines the replaceable event `kind:34550` to define the community and the current list of moderators/administrators. Users that want to post into the community, simply tag any Nostr event with the community's `a` tag. Moderators issue an approval event `kind:4550` that links the community with the new post.
+The goal of this NIP is to create moderator-approved public communities around a topic. It defines the replaceable event `kind:34550` to define the community and the current list of moderators/administrators. Users that want to post into the community, simply tag any Nostr event with the community's `a` tag.  Users that want to post *exclusively* into the community send an event `kind:4549`. Moderators issue an approval event `kind:4550` that links the community with the new post.
 
 # Community Definition
 
@@ -55,6 +55,48 @@ Any Nostr event can be a post request. Clients MUST add the community's `a` tag
   "content": "<My content>"
 }
 ```
+# New Post Request (Exclusive to community audience)
+
+When we use kind 1, the note can show up in other clients without context, creating confusion.
+
+To create a kind 1 post exclusive to a community's audience, clients MUST use kind `4549` with the same `a` tag as above and MAY add an additional `k` tag with value `"1"`
+
+```json
+{
+  "id": "<32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>",
+  "pubkey": "<32-bytes lowercase hex-encoded public key of the event creator>",
+  "created_at": <Unix timestamp in seconds>,
+  "kind": 4549,
+  "tags": [
+    ["a", "34550:<Community event author pubkey>:<d-identifier of the community>", "<Optional relay url>"],
+    ["k", "1"]
+  ],
+  "content": "<My content>"
+}
+```
+
+# Support for Different Event Kinds
+Nostr communities are not just for kind `1` events.  Clients can send any valid nostr event exclusively to a specific community's audience by wrapping the event in a `4549` kind event.
+
+Additionally, the clients MUST add a `k` tag with value of the kind of event to be posted.
+
+For example, if the user wants to publish a long-form post exclusively to a community, then the post request `kind:4549` event should contain a `k` tag with value `30023`, while retaining the same `content` as if creating a long-form post as defined in [NIP-23](23.md)
+
+Clients MAY assume any event of kind `4549` without a `k` tag to be of kind `1`.
+
+```json
+{
+  "id": "<32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>",
+  "pubkey": "<32-bytes lowercase hex-encoded public key of the event creator>",
+  "created_at": <Unix timestamp in seconds>,
+  "kind": 4549,
+  "tags": [
+    ["a", "34550:<Community event author pubkey>:<d-identifier of the community>", "<Optional relay url>"],
+    ["k", "<event kind>"]
+  ],
+  "content": "<My content>"
+}
+```
 
 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)).
 
@@ -80,7 +122,12 @@ The post-approval event MUST include `a` tags of the communities the moderator i
 
 It's recommended that multiple moderators approve posts to avoid deleting them from the community when a moderator is removed from the owner's list. In case the full list of moderators must be rotated, the new moderator set must sign new approvals for posts in the past or the community will restart. The owner can also periodically copy and re-sign of each moderator's approval events to make sure posts don't disappear with moderators.
 
-Post Approvals of replaceable events can be created in three ways: (i) by tagging the replaceable event as an `e` tag if moderators want to approve each individual change to the repleceable event; (ii) by tagging the replaceable event as an `a` tag if the moderator authorizes the replaceable event author to make changes without additional approvals and (iii) by tagging the replaceable event with both its `e` and `a` tag which empowers clients to display the original and updated versions of the event, with appropriate remarks in the UI. Since relays are instructed to delete old versions of a replaceable event, the `.content` of an `e`-approval MUST have the specific version of the event or Clients might not be able to find that version of the content anywhere.
+Post Approvals of replaceable events can be created in three ways: 
+  1. by tagging the replaceable event as an `e` tag if moderators want to approve each individual change to the replaceable event; 
+  2. by tagging the replaceable event as an `a` tag if the moderator authorizes the replaceable event author to make changes without additional approvals and 
+  3. by tagging the replaceable event with both its `e` and `a` tag which empowers clients to display the original and updated versions of the event, with appropriate remarks in the UI. 
+
+Since relays are instructed to delete old versions of a replaceable event, the `.content` of an `e`-approval MUST have the specific version of the event or Clients might not be able to find that version of the content anywhere.
 
 Clients SHOULD evaluate any non-`34550:*` `a` tag as posts to be included in all `34550:*` `a` tags.
 
@@ -90,7 +137,7 @@ Community clients SHOULD display posts that have been approved by at least 1 mod
 
 The following filter displays the approved posts.
 
-```js
+```json
 {
   "authors": ["<Author pubkey>", "<Moderator1 pubkey>", "<Moderator2 pubkey>", "<Moderator3 pubkey>", ...],
   "kinds": [4550],

README.md

@@ -92,6 +92,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `1311`  | Live Chat Message          | [53](53.md) |
 | `1984`  | Reporting                  | [56](56.md) |
 | `1985`  | Label                      | [32](32.md) |
+| `4549`  | Community Exclusive Post   | [72](72.md) |
 | `4550`  | Community Post Approval    | [72](72.md) |
 | `9734`  | Zap Request                | [57](57.md) |
 | `9735`  | Zap                        | [57](57.md) |