Kind 10000: Mute List

Overview

Mute List events (kind 10000) allow users to define and share the content they don't want to see in their feeds. This standard replaceable event kind acts as a filter, specifying public keys of users, hashtags, specific words, or entire threads that should be hidden from the user's view. Mute lists can include both public items (visible in the event tags) and private items (encrypted in the content field).

Specification

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

Content Format

The content field can contain encrypted private mute items using NIP-04 encryption. The encrypted content follows the same structure as the public tags but is only visible to the creator. The encryption uses a shared key computed from the author's public and private key.

Schema

For encrypted private mute items:

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

The encrypted content, when decrypted, would reveal a JSON array of tags:

[
  ["p", "<pubkey-to-mute>"],
  ["t", "<hashtag-to-mute>"],
  ["word", "<word-to-mute>"],
  ["e", "<thread-to-mute>"]
]

Tags

Tag Name	Description	Format	Required
p	Public key to mute	["p", "<pubkey-hex>"]	No
t	Hashtag to mute	["t", "<hashtag>"]	No
word	Word to mute (lowercase)	["word", "<lowercase-word>"]	No
e	Thread ID to mute	["e", "<event-id>"]	No

Client Behavior

Clients should:

1. Read the user's mute list when loading content
2. Filter out content from muted public keys
3. Hide posts containing muted hashtags
4. Hide posts containing muted words (case-insensitive matching recommended)
5. Hide threads identified by muted thread IDs
6. Provide an interface for users to add and remove items from their mute list
7. Support both public (in tags) and private (encrypted in content) mute items
8. When processing content from the encrypted part, decrypt it using NIP-04 and the user's keys
9. Consider supporting importing mute lists from trusted users

Relay Behavior

Relays should:

1. Handle kind 10000 events as normal replaceable events
2. Store these events to allow clients to retrieve the user's mute list
3. Not attempt to interpret or enforce the mute preferences (this is client-side functionality)

Use Cases

• Blocking spam accounts
• Filtering out content on topics the user isn't interested in
• Hiding offensive words or terms
• Muting noisy conversations or threads
• Curating a more enjoyable feed experience
• Avoiding content from known bad actors or trolls
• Creating temporary mutes for trending topics that temporarily overwhelm a feed

Example

{
  "id": "a92a316b75e44cfdc19986c634049158d4206fcc0b7b9c7ccbcdabe28beebcd0",
  "pubkey": "854043ae8f1f97430ca8c1f1a090bdde6488bd5115c7a45307a2a212750ae4cb",
  "created_at": 1699597889,
  "kind": 10000,
  "tags": [
    ["p", "07caba282f76441955b695551c3c5c742e5b9202a3784780f8086fdcdc1da3a9"],
    ["p", "a55c15f5e41d5aebd236eca5e0142789c5385703f1a7485aa4b38d94fd18dcc4"],
    ["t", "politics"],
    ["word", "spoiler"],
    ["e", "d78ba0d5dce22bfff9db0a9e996c9ef27e2c91051de0c4e1da340e0326b4941e"]
  ],
  "content": "TJob1dQrf2ndsmdbeGU+05HT5GMnBSx3fx8QdDY/g3NvCa7klfzgaQCmRZuo1d3WQjHDOjzSY1+MgTK5WjewFFumCcOZniWtOMSga9tJk1ky00tLoUUzyLnb1v9x95h/iT/KpkICJyAwUZ+LoJBUzLrK52wNTMt8M5jSLvCkRx8C0BmEwA==?iv=S3rFeFr1gsYqmQA7bNnNTQ==",
  "sig": "1173822c53261f8cffe7efbf43ba4a97a9198b3e402c2a1df130f42a8985a2d0d3430f4de350db184141e45ca844ab4e5364ea80f11d720e36357e1853dba6ca"
}

Encryption Process

To add private mute items, clients should:

1. Create a JSON array of tags for items to mute privately
2. Encrypt this array using NIP-04 with a shared key derived from the user's own public and private key
3. Store the encrypted content in the event's content field

Pseudocode:

private_items = [
  ["p", "07caba282f76441955b695551c3c5c742e5b9202a3784780f8086fdcdc1da3a9"],
  ["word", "nsfw"]
]
encrypted_content = nip04.encrypt(json.stringify(private_items), user_private_key, user_public_key)
event.content = encrypted_content

References

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

Related Kinds

• Kind 30000: Follow Sets - Categorized lists of followed profiles
• Kind 30007: Kind Mute Sets - Mute users for specific event kinds
• Kind 10001: Pinned Notes - Events the user wants to showcase in their profile
• Kind 10003: Bookmarks - Things a user wants to save

Notes

• The mute list is one of several standard list types defined in NIP-51
• Users can only have one mute list (since it's a replaceable event)
• Mute list items can target people (p tag), topics (t tag), specific words (word tag), or entire threads (e tag)
• For maximum privacy, sensitive mute items can be encrypted so that only the user can see them
• When new items are added to an existing mute list, clients should append them to the end of the list to maintain chronological order
• Clients should implement case-insensitive matching for muted words
• A deprecated version of mute lists used kind 30000 with a "d" tag value of "mute"