Nostrbook

Appearance

Kind 44: Channel Mute User ​

Overview ​

Kind 44 events are part of the public chat system (NIP-28) and provide a client-side moderation mechanism for muting specific users in a channel. When a user creates a kind 44 event targeting another user's public key, clients should hide all messages from that user when displaying channel content to the muting user. This allows individuals to customize their chat experience without requiring relay-side moderation.

Specification ​

PropertyValue
Kind Number44
Event RangeRegular
Defined inNIP-28

Content Format ​

The content field is optional and may include metadata about the mute action, such as the reason for muting the user. It should be a JSON string if provided.

Schema ​

json
"content": "{\"reason\": \"Persistent spam\"}"

Tags ​

Tag NameDescriptionFormatRequired
pPublic key of user to mute["p", "<pubkey>"]Yes

Client Behavior ​

Clients should:

  1. Hide any kind 42 (channel message) events from a public key if the current user has created a kind 44 event referencing that public key
  2. Allow users to easily create kind 44 events when they want to mute specific users in channels
  3. Optionally support providing a reason when muting a user
  4. Optionally implement collective moderation by hiding messages from users that multiple people have muted for certain reasons

Relay Behavior ​

Relays are not required to perform any special handling for kind 44 events. They should:

  1. Store and serve these events like any other regular event
  2. Not be expected to filter messages based on these events, as the filtering is handled client-side

Use Cases ​

  • Personal content filtering in public chat channels
  • Hiding all messages from users that are disruptive or posting unwanted content
  • Creating safe, moderated environments without requiring relay-side moderation
  • Collective moderation through aggregating user mute actions
  • Building client-specific moderation policies based on user preferences

Example ​

json
{
  "id": "4376c65d2f232afbe9b882a35baa4f6fe8667c4e684749af565f981833ed6a65",
  "pubkey": "79dff8f82963424e0bb02708a22e44b4980893e3a4be0fa3cb60a43b946764e3",
  "created_at": 1671217411,
  "kind": 44,
  "tags": [
    ["p", "3c9849383bdea883b0bd16fece1ed36d37e37cdde3ce43b17ea4e9192ec11289"]
  ],
  "content": "{\"reason\": \"Repeatedly posting spam\"}",
  "sig": "908a15e46fb4d8675bab026fc230a0e3542bfade63da02d542fb78b2a8513fcd0092619a2c8c1221e581946e0191f2af505dfdf8657a414dbca329186f009262"
}

Example with no reason provided:

json
{
  "id": "fe8b1c9a37218cf5ce604a8dce596c9c3ae0c650df2336f3c60c78e61a7b2031",
  "pubkey": "f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca",
  "created_at": 1671217500,
  "kind": 44,
  "tags": [
    ["p", "f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca"]
  ],
  "content": "",
  "sig": "a76f39224cebd44cf04eeebe01d5ab2e8f7a3e5e56c83cadd252e7bc5e2e34fd7ad7148cf7a2c7620d9490ccf2e1bac521995725f2e1f543159b8eb98bfdd405"
}

References ​

Notes ​

  • The mute action is personal to the user who created the kind 44 event - it doesn't affect how messages are displayed to other users by default
  • Clients may choose to implement collective moderation by aggregating mute events from multiple users
  • Unlike kind 43 (hide message) which targets a specific message, kind 44 hides all messages from a particular user
  • This provides a more comprehensive moderation tool when a user consistently posts unwanted content
  • The content field is optional but can be useful for categorizing reasons for moderation and implementing sophisticated filtering policies
  • There is no direct mechanism to "unmute" a user except by creating a new kind 44 event that might be interpreted by clients as an override
  • In practice, clients should consider the most recent kind 44 event from a user regarding another user as the current mute status