{"id":"f66dc18aa7f18bf8eb209d3e98df1c21dc39eb1ae519d5a6253af5e4e9a09bf5","pubkey":"0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd","created_at":1749154819,"kind":30817,"tags":[["d","chorus"],["title","Chorus NIP-72 Extensions"],["k","34551"],["k","34552"],["k","34553"],["k","34554"],["k","34555"],["k","4551"],["k","4552"],["k","4553"],["k","4554"],["client","nostrhub.io"]],"content":"# Chorus NIP-72 Extensions\n\n`draft` `optional`\n\n**⚠️ DISCLAIMER: This NIP is still under active development and subject to change. The event kinds and specifications described here are experimental and may be modified, deprecated, or replaced in future versions. It is not recommended to implement this NIP in production systems without first discussing it with the Chorus development team.**\n\nThis document describes the Chorus platform's extensions to NIP-72 (Moderated Communities) that enhance community management, user moderation, and content organization capabilities.\n\n## Background\n\nNIP-72 defines the basic framework for moderated communities on Nostr using:\n- **Kind 34550**: Community definition events\n- **Kind 4550**: Post approval events\n\nChorus extends this foundation with additional event kinds to provide comprehensive community management features including member lists, content pinning, join requests, and enhanced moderation workflows.\n\n## Core NIP-72 Event Kinds\n\n### Kind 34550: Community Definition\nDefines a community with metadata and moderator lists as specified in NIP-72.\n\n### Kind 4550: Post Approval  \nModerator approval events for posts as specified in NIP-72.\n\n## Chorus Extensions\n\n### Member Management Events\n\n#### Kind 34551: Approved Members List\n**Addressable event** that maintains a list of users who are pre-approved to post in the community without requiring individual post approvals.\n\n**Tags:**\n- `[\"d\", communityId]` - Identifies which community this list belongs to\n- `[\"p\", pubkey]` - One tag per approved member\n\n**Example:**\n```json\n{\n  \"kind\": 34551,\n  \"pubkey\": \"moderator_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"d\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"p\", \"approved_user_1_pubkey\"],\n    [\"p\", \"approved_user_2_pubkey\"],\n    [\"p\", \"approved_user_3_pubkey\"]\n  ],\n  \"content\": \"\"\n}\n```\n\n#### Kind 34552: Declined Members List\n**Addressable event** that tracks users whose join requests have been declined.\n\n**Tags:**\n- `[\"d\", communityId]` - Identifies which community this list belongs to  \n- `[\"p\", pubkey]` - One tag per declined user\n\n**Example:**\n```json\n{\n  \"kind\": 34552,\n  \"pubkey\": \"moderator_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"d\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"p\", \"declined_user_1_pubkey\"],\n    [\"p\", \"declined_user_2_pubkey\"]\n  ],\n  \"content\": \"\"\n}\n```\n\n#### Kind 34553: Banned Members List\n**Addressable event** that maintains a list of users who are banned from the community.\n\n**Tags:**\n- `[\"d\", communityId]` - Identifies which community this list belongs to\n- `[\"p\", pubkey]` - One tag per banned user\n\n**Example:**\n```json\n{\n  \"kind\": 34553,\n  \"pubkey\": \"moderator_pubkey\", \n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"d\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"p\", \"banned_user_1_pubkey\"],\n    [\"p\", \"banned_user_2_pubkey\"]\n  ],\n  \"content\": \"\"\n}\n```\n\n### Content Organization Events\n\n#### Kind 34554: Pinned Posts List\n**Addressable event** that maintains a list of posts pinned by community moderators.\n\n**Tags:**\n- `[\"d\", communityId]` - Identifies which community this list belongs to\n- `[\"e\", eventId]` - One tag per pinned post\n\n**Example:**\n```json\n{\n  \"kind\": 34554,\n  \"pubkey\": \"moderator_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"d\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"e\", \"pinned_post_1_id\"],\n    [\"e\", \"pinned_post_2_id\"],\n    [\"e\", \"pinned_post_3_id\"]\n  ],\n  \"content\": \"\"\n}\n```\n\n#### Kind 34555: Pinned Groups List\n**Addressable event** that allows users to maintain a personal list of their favorite/pinned communities.\n\n**Tags:**\n- `[\"d\", \"pinned-groups\"]` - Identifies this as the user's pinned groups list\n- `[\"a\", communityId]` - One tag per pinned community\n\n**Example:**\n```json\n{\n  \"kind\": 34555,\n  \"pubkey\": \"user_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"d\", \"pinned-groups\"],\n    [\"a\", \"34550:creator1_pubkey:bitcoin-discussion\"],\n    [\"a\", \"34550:creator2_pubkey:nostr-development\"],\n    [\"a\", \"34550:creator3_pubkey:photography\"]\n  ],\n  \"content\": \"\"\n}\n```\n\n### Moderation Action Events\n\n#### Kind 4551: Post Removal\n**Regular event** that indicates a moderator has removed a post from the community.\n\n**Tags:**\n- `[\"a\", communityId]` - References the target community\n- `[\"e\", eventId]` - References the removed post\n- `[\"p\", authorPubkey]` - References the post author\n- `[\"k\", originalKind]` - Kind of the original post\n\n**Content:**\nThe content field can be left blank or optionally include a moderation reason.\n\n**Example:**\n```json\n{\n  \"kind\": 4551,\n  \"pubkey\": \"moderator_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"a\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"e\", \"removed_post_id\"],\n    [\"p\", \"post_author_pubkey\"],\n    [\"k\", \"1\"]\n  ],\n  \"content\": \"Removed for violating community guidelines\"\n}\n```\n\n#### Kind 4552: Join Request\n**Regular event** that represents a user's request to join a community.\n\n**Tags:**\n- `[\"a\", communityId]` - References the target community\n\n**Example:**\n```json\n{\n  \"kind\": 4552,\n  \"pubkey\": \"requesting_user_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"a\", \"34550:community_creator_pubkey:bitcoin-discussion\"]\n  ],\n  \"content\": \"I would like to join this community to discuss Bitcoin topics.\"\n}\n```\n\n#### Kind 4553: Leave Request  \n**Regular event** that represents a user's request to leave a community.\n\n**Tags:**\n- `[\"a\", communityId]` - References the target community\n\n**Example:**\n```json\n{\n  \"kind\": 4553,\n  \"pubkey\": \"leaving_user_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"a\", \"34550:community_creator_pubkey:bitcoin-discussion\"]\n  ],\n  \"content\": \"I am leaving this community.\"\n}\n```\n\n#### Kind 4554: Close Report\n**Regular event** that indicates a moderator has resolved a report (Kind 1984).\n\n**Tags:**\n- `[\"e\", reportId]` - References the original report event\n- `[\"a\", communityId]` - References the target community  \n- `[\"t\", actionType]` - Indicates the action taken (e.g., \"content removed\", \"user banned\", \"closed without action\")\n\n**Example:**\n```json\n{\n  \"kind\": 4554,\n  \"pubkey\": \"moderator_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"e\", \"original_report_id\"],\n    [\"a\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"t\", \"content removed\"]\n  ],\n  \"content\": \"Report resolved: Content violated community guidelines and has been removed.\"\n}\n```\n\n### Enhanced Post Events\n\n#### Kind 11: Group Post\nStandard text note posted to a community, extending Kind 1 with community targeting.\n\n**Tags:**\n- `[\"a\", communityId]` - References the target community\n\n**Example:**\n```json\n{\n  \"kind\": 11,\n  \"pubkey\": \"user_pubkey\",\n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"a\", \"34550:community_creator_pubkey:bitcoin-discussion\"]\n  ],\n  \"content\": \"What do you think about the latest Bitcoin price movement?\"\n}\n```\n\n#### Kind 1111: Group Post Reply\nReply to a group post, enabling threaded discussions within communities.\n\n**Tags:**\n- `[\"a\", communityId]` - References the target community\n- `[\"e\", parentPostId]` - References the parent post being replied to\n- `[\"p\", parentAuthorPubkey]` - References the author of the parent post\n\n**Example:**\n```json\n{\n  \"kind\": 1111,\n  \"pubkey\": \"replying_user_pubkey\", \n  \"created_at\": 1234567890,\n  \"tags\": [\n    [\"a\", \"34550:community_creator_pubkey:bitcoin-discussion\"],\n    [\"e\", \"parent_post_id\"],\n    [\"p\", \"parent_post_author_pubkey\"]\n  ],\n  \"content\": \"I think the price movement is due to institutional adoption increasing.\"\n}\n```\n\n## Implementation Notes\n\n### Addressable vs Regular Events\n\n**Addressable Events (3455x kinds)** use `[\"d\", identifier]` tags for self-identification:\n- Kind 34550: Community definitions\n- Kind 34551: Approved members lists  \n- Kind 34552: Declined members lists\n- Kind 34553: Banned members lists\n- Kind 34554: Pinned posts lists\n- Kind 34555: Pinned groups lists\n\n**Regular Events (455x kinds)** use `[\"a\", communityId]` tags to reference communities:\n- Kind 4550: Post approvals\n- Kind 4551: Post removals\n- Kind 4552: Join requests\n- Kind 4553: Leave requests  \n- Kind 4554: Close reports\n\n### Auto-Approval Workflow\n\nPosts from users in the approved members list (Kind 34551) are automatically considered approved without requiring individual Kind 4550 approval events. This reduces moderation overhead for trusted community members.\n\n### Moderation Hierarchy\n\n1. **Community Creator**: Has full control over the community\n2. **Moderators**: Listed in the community definition with `[\"p\", pubkey, relay, \"moderator\"]` tags\n3. **Approved Members**: Can post without individual approval\n4. **Regular Members**: Posts require moderator approval\n5. **Banned Users**: Cannot post, all content hidden\n\n### Client Implementation\n\nClients SHOULD:\n- Display approved posts by default\n- Provide toggles to view pending/unapproved content for moderators\n- Hide content from banned users\n- Show visual indicators for pinned posts\n- Implement join request workflows for private communities\n- Support threaded replies within communities\n\n## Security Considerations\n\n- Member lists should only be updated by community moderators\n- Clients should verify moderator permissions before displaying moderation actions\n- Banned user lists should be respected across all community interactions\n- Report resolution events should only be created by authorized moderators\n\n## Compatibility\n\nThese extensions are designed to be backward compatible with NIP-72. Clients that only implement basic NIP-72 will still function but may not display the enhanced moderation and organization features.","sig":"810cff53b33a678ebceadfd60e23f8b1a35d817d5f960b4f96d6217789bc2191587ca4415c4134e23faa7976343783070cf4ac9f608ce773c7734960f1aeddde"}