Kind 30007: Kind Mute Sets

Overview

Kind Mute Sets events (kind 30007) allow users to selectively mute specific users for particular event kinds only. This parameterized replaceable event kind enables more granular control than a global mute list, letting users filter out certain types of content from specific authors while still seeing their other content. For example, a user could mute someone's reposts (kind 6) without muting their original notes (kind 1).

Specification

Property	Value
Kind Number	30007
Event Range	Parameterized Replaceable
Defined in	NIP-51

Content Format

The content field can contain encrypted private mute entries using NIP-04 encryption. The encrypted content follows the same structure as the public tags but is only visible to the creator. It can also contain a description or notes about the mute set.

Schema

For encrypted private mute entries:

"content": "<NIP-04 encrypted JSON array of tags>"

For descriptive content:

"content": "People whose reposts I don't want to see."

Tags

Tag Name	Description	Format	Required
d	Must be the kind number to mute	["d", "<kind-number>"]	Yes
p	Public key to mute for this kind	["p", "<pubkey-hex>"]	Yes
description	Description of the mute set	["description", "<description-text>"]	No

Client Behavior

Clients should:

1. Check these events when filtering content
2. Hide events of the specified kind from the specified pubkeys
3. Continue to display other kinds of events from those pubkeys
4. Use the d tag value (kind number) to determine which event types to filter
5. Provide an interface for users to add or remove pubkeys from kind-specific mute sets
6. Handle both public (in tags) and private (encrypted in content) mute entries
7. When processing encrypted mute entries, decrypt using NIP-04 and the user's keys
8. Maintain the chronological order of entries, with newest additions at the end
9. Combine filtering with the global mute list (kind 10000) for comprehensive content control

Relay Behavior

Relays should:

1. Handle kind 30007 events as parameterized replaceable events with the d tag as discriminator
2. Store these events to allow clients to retrieve the user's kind mute sets
3. Not attempt to interpret or enforce muting (this is client-side functionality)

Use Cases

• Muting someone's reposts while still seeing their original content
• Filtering out reactions but keeping notes from certain users
• Hiding long-form articles from users who post too many
• Muting someone in public chats but not in direct messages
• Creating targeted content filtering based on both author and content type
• Reducing noise in feeds by filtering specific types of content
• Managing content visibility with granular control

Example

{
  "id": "43b7f9fc65d9f1bf1580159a8f096151c92118e6be84ff48e006a31fe7a8d689",
  "pubkey": "854043ae8f1f97430ca8c1f1a090bdde6488bd5115c7a45307a2a212750ae4cb",
  "created_at": 1699597889,
  "kind": 30007,
  "tags": [
    ["d", "6"],
    ["description", "People whose reposts I don't want to see"],
    ["p", "07caba282f76441955b695551c3c5c742e5b9202a3784780f8086fdcdc1da3a9"],
    ["p", "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"],
    ["p", "a55c15f5e41d5aebd236eca5e0142789c5385703f1a7485aa4b38d94fd18dcc4"]
  ],
  "content": "These accounts repost too much content that isn't relevant to me.",
  "sig": "a9a4e2192eede77e6c9d24ddfab95ba3ff7c03fbd07ad011fff245abea431fb4d3787c2d04aad001cb039cb8de91d83ce30e9a94f82ac3c5a2372aa1294a96bd"
}

Another example for muting long-form content:

{
  "id": "732f8e92f26b5773f37e53808d6944e883bd018fc7b2474a6ddfd9fd9707f8e5",
  "pubkey": "854043ae8f1f97430ca8c1f1a090bdde6488bd5115c7a45307a2a212750ae4cb",
  "created_at": 1699598000,
  "kind": 30007,
  "tags": [
    ["d", "30023"],
    ["description", "People whose articles I don't want to see"],
    ["p", "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"]
  ],
  "content": "",
  "sig": "b317a8d33e65cdd0ca642a42934e11b26cd4c1ed1d63e12a5e3b83d4e23ea6aa06c1891a80dd0a3e4f56bb86aae4b4fb194b5733ad6fbe247e4a1abd86a3f70"
}

References

• NIP-51: Lists
• NIP-04: Encrypted Direct Messages

Related Kinds

• Kind 10000: Mute List - Global mute list for all content types
• Kind 1: Short Text Note - Common event kind that might be selectively muted
• Kind 6: Repost - Common event kind that might be selectively muted
• Kind 30023: Long-form Content - Common event kind that might be selectively muted

Notes

• Kind Mute Sets are parameterized lists, allowing users to have multiple sets with different d tag values
• The d tag for Kind Mute Sets MUST contain a kind number, unlike other list types where it can be any identifier
• Multiple Kind Mute Sets can co-exist, each for a different event kind
• This provides more precise content filtering than the global mute list (kind 10000)
• Kind-specific muting is particularly useful for filtering out specific content types from prolific posters
• Privacy considerations should be taken into account when creating mute lists; using encrypted content sections can hide your muting preferences
• Clients should implement these filters client-side, as relay-side filtering could reveal muting preferences