Kind 1984: Reporting

Overview

Kind 1984 events enable users to report objectionable content in the Nostr ecosystem. These reports signal to other users, clients, and relays that specific content may be problematic. The definition of "objectionable" is subjective, and all parties on the network (users, applications, relays) can consume and act on reports as they see fit. This kind provides a standardized mechanism for community moderation without imposing centralized content policies.

Specification

Property	Value
Kind Number	1984
Event Range	Regular
Defined in	NIP-56

Content Format

The content field may contain additional information submitted by the reporting entity, explaining the reason for the report or providing context.

Schema

"content": "This profile contains misleading information and is impersonating a well-known figure."

Tags

Tag Name	Description	Format	Required
p	Reported public key	["p", "<pubkey>", "<report-type>"]	Yes
e	Reported event	["e", "<event-id>", "<report-type>"]	Conditional*
x	Reported blob hash	["x", "<blob-hash>", "<report-type>"]	Conditional*
server	Server containing blob	["server", "<server-url>"]	No
L	Label namespace	["L", "<namespace>"]	No
l	Label	["l", "<label-id>", "<namespace>"]	No

*At least one of p, e, or x tags must be present with a report type.

Report Types

The third entry in the p, e, or x tag specifies the type of report:

Report Type	Description
nudity	Depictions of nudity, pornography, etc.
malware	Virus, trojan horse, spyware, ransomware, etc.
profanity	Profanity, hateful speech, etc.
illegal	Content that may be illegal in some jurisdictions
spam	Unsolicited, repetitive content
impersonation	Someone pretending to be someone else
other	Reports that don't fit in the above categories

Client Behavior

Clients should:

1. Allow users to create and submit reports for objectionable content
2. Consider using reports from users' social connections to make moderation decisions
3. Provide options for automatic content filtering based on report volumes or sources
4. Implement appropriate UI for reporting that includes selecting report types
5. Optionally use the NIP-32 labeling system for more granular report categorization

Relay Behavior

Relays should:

1. Store and serve report events like other regular events
2. Exercise caution with automated moderation based on reports, as they can be gamed
3. Optionally use reports from trusted sources to enforce relay-specific content policies

Use Cases

• Community-based content moderation
• Warning others about potentially harmful content
• Identifying spam or malicious actors
• Reporting impersonation attempts
• Filtering explicit content based on personal preferences
• Creating social trust networks for moderation

Example

Report of a profile for impersonation:

{
  "id": "4376c65d2f232afbe9b882a35baa4f6fe8667c4e684749af565f981833ed6a65",
  "pubkey": "79dff8f82963424e0bb02708a22e44b4980893e3a4be0fa3cb60a43b946764e3",
  "created_at": 1671217411,
  "kind": 1984,
  "tags": [
    ["p", "f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca", "impersonation"]
  ],
  "content": "This profile is impersonating nostr:npub1abcdefghijklmnopqrstuvwxyz0123456789abcdefghijklmnopqrstuv",
  "sig": "908a15e46fb4d8675bab026fc230a0e3542bfade63da02d542fb78b2a8513fcd0092619a2c8c1221e581946e0191f2af505dfdf8657a414dbca329186f009262"
}

Report of an event with illegal content:

{
  "id": "fe8b1c9a37218cf5ce604a8dce596c9c3ae0c650df2336f3c60c78e61a7b2031",
  "pubkey": "79dff8f82963424e0bb02708a22e44b4980893e3a4be0fa3cb60a43b946764e3",
  "created_at": 1671217500,
  "kind": 1984,
  "tags": [
    ["e", "a1a2a3a4b1b2b3b4c1c2c3c4d1d2d3d4e1e2e3e4f1f2f3f4aaabbbcccddd", "illegal"],
    ["p", "f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca"]
  ],
  "content": "This post contains content that appears to violate local regulations regarding financial advice.",
  "sig": "a76f39224cebd44cf04eeebe01d5ab2e8f7a3e5e56c83cadd252e7bc5e2e34fd7ad7148cf7a2c7620d9490ccf2e1bac521995725f2e1f543159b8eb98bfdd405"
}

Report of a blob with malware:

{
  "id": "a6c49604e8b105829f27804c56ba1eef8c487ceabc1a2eaffab3d9c9a312dfca",
  "pubkey": "79dff8f82963424e0bb02708a22e44b4980893e3a4be0fa3cb60a43b946764e3",
  "created_at": 1671218000,
  "kind": 1984,
  "tags": [
    ["x", "3a9a34a15b6cd1cb56741f47ea7c0e64c57fc8abb5a9b99e9f16c9c55115c56b", "malware"],
    ["e", "5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36", "malware"],
    ["server", "https://example.com/files/suspicious_file.exe"]
  ],
  "content": "This file contains malware that attempts to steal user credentials.",
  "sig": "5f8ac6d9c2dab830ebbdb231ad6123ef0121c4710218f339d9d3b5b22fd74c0a7b1be0de52ffce6022e87dfa5b7ae3f2749a126b09c82c3ea31eb4c69d25091c"
}

References

• NIP-56: Reporting
• NIP-32: Labeling (for L and l tags)

Related Kinds

• Kind 1: Short Text Note - Events that might be reported
• Kind 0: User Metadata - Profiles that might be reported for impersonation
• Kind 1063: File Metadata - Files that might be reported for malware or objectionable content

Notes

• The kind number 1984 is a reference to George Orwell's novel dealing with surveillance and censorship, chosen to emphasize the importance of using this mechanism responsibly
• Reports are subjective by nature, and different cultural contexts may lead to different interpretations of what constitutes objectionable content
• Clients should be cautious about automatic actions based solely on report volume, as reporting systems can be abused
• Using reports from trusted social connections can create effective community moderation without centralized control
• Some report types (like "impersonation") are more applicable to profiles than to individual events