← Back to Nostr Implementation Possibilities
NIP 36specificationdraftkey-managementeventschain-identification

Sensitive Content / Content Warning

The `content-warning` tag enables users to specify if the event's content needs to be approved by readers to be shown. Clients can hide the content until the user acts on it.

No reviews
Unknown·Updated Mar 29, 2026·0 reviews·0 attestations·View source
Collections:NIPs — Merged

Specification

The content-warning tag enables users to specify if the event's content needs to be approved by readers to be shown. Clients can hide the content until the user acts on it.

l and L tags MAY be also be used as defined in NIP-32 with the content-warning or other namespace to support further qualification and querying.

Spec

tag: content-warning
options:
 - [reason]: optional

Example

{
  "pubkey": "<pub-key>",
  "created_at": 1000000000,
  "kind": 1,
  "tags": [
    ["t", "hastag"],
    ["L", "content-warning"],
    ["l", "reason", "content-warning"],
    ["L", "social.nos.ontology"],
    ["l", "NS-nud", "social.nos.ontology"],
    ["content-warning", "<optional reason>"]
  ],
  "content": "sensitive content with #hastag\n",
  "id": "<event-id>"
}

Discussion (0 threads)

Loading discussions...