If NIP-36 is being used to self-report one's profile the user may classify the entire profile and/or just parts of a profile by appending the item name for the applicable part of the profile to the content type or context code. For example:

##### Content warnings for particular components of a profile

``` tag: content-warning options: - [reason]: may be a null or blank - [codes]: mandatory ``` The [reason] option was defined in NIP-36. It may be null or a blank string.

#### Use with NIP-36 self-reported "content warnings"

To use with NIP-56 simply replace the original 5 defined report types (`Old Code` above) with the 2 or 6 character codes above.

### How to use type and context codes Only the codes (`TypeCode` and `ContextCode` above) should go over the wire. The descriptions and notes should only be used in user interfaces. #### Use with NIP-56 after the fact reports

ContextCode | Context --- | --- ED | Educational FA | Fine Art FF | Fantasy / Fiction MS | Medical / Scientific ND | News & Documentaries PP | Political Protest

**_Format:_ AB** - where 'AB' is a mandatory 2 character, uppercase code of a major content type category

### Contexts

TypeCode | Old Code | Type | Notes --- | --- | --- | --- CL | profanity | Coarse Language / Profanity | HC-fin | | Promotion of content that is likely to cause financial ruin | consider also IL-frd HC-bhd | | Promotion of content that is likely to cause serious bodily harm or death | IH | | Intolerance & Hate | does not include intolerance of intolerance | IL | illegal | Illegal Content | post/profile is illegal or advocates illegal activity IL-cop | | Copyright violation, piracy, intellectual property theft | IL-csa | | Child sexual abuse and/or trafficking | IL-drg | | Drug-related crime | IL-frd | | Fraud & Scams | IL-har | | Harassment / stalking / doxxing | IL-hkr | | Prostitution | IL-idt | Impersonation | Impersonation / Identity theft / phishing | IL-mal | | Malware / viruses / ransomware | NS | nudity | Nudity & Sex | NS-nud | | Casual nudity | NS-ero | | Erotica | NS-sex | | Sex | PG | | No Sensitive Content | for use in situations where sensitive content might be assumed PN | | Pornography | PN-het | | Heterosexual porn | PN-gay | | Gay male porn | PN-les | | Lesbian porn | PN-bis | | Bisexual porn | PN-trn | | Transsexual porn | PN-fnb | | Gender-fluid / non-binary porn | SP | spam | Spam | SP-mod | | Moderation report spam | VI | | Violence | actual or advocated | VI-hum | | Violence towards a human being | VI-ani | | Violence towards a sentient animal |

### Reportable Types These types expand and standardize the `report type` defined in NIP-56. Existing NIP-56 report types (`Old Code` in table below) should be supported by clients for backwards compatibility, but should not otherwise be used in future development.

### Context To facilitate effective content moderation, all forms of content warning/reporting - whether self-reporting at the time of the post (via a [NIP-36](https://github.com/nostr-protocol/nips/blob/master/36.md) `content-warning`) or after the fact reporting (via [NIP-56](https://github.com/nostr-protocol/nips/blob/master/56.md)) - need to be handled in a consistent manner. For example a person could use NIP-56 to correct a missing or inaccurate NIP-36 designation on one of their own posts and the NIP-56 report should be handled the same as a NIP-36 content warning in the original post. Because of the overlap in the two types of reports, and in order to facilitate effective and efficient content moderation by relays and clients, the development of a common, translatable "vocabulary" to use in those reports is the first step in aligning the use of those reports.

````suggestion Self-reporting a post: ``` { "pubkey": <pubkey>, "kind": 1, "tags": [ ["t", "hashtag"], ["content-warning", "Wet t-shirt contest", "NS-ero"] ], "content": "(Racy content goes here)", "id": <eventId> } ``` 3rd party reporting of same post: ``` { "kind": 1984, "tags": [ [ "e", <eventId>, "NS-ero"], [ "p", <pubkey>] ], "content": "Wet t-shirt contest", ... } ``` Self-reporting of an entire profile: ``` { "id": <eventId>, "pubkey": <pubkey>, "created_at": 1000000000, "kind": 0, "tags": [ ["t", "hashtag"], ["content-warning", "Posts frequently feature drawings of naked people.", "NS-nud,FA"] ], "content": "{\"name\":\"OttawaLifeDrawing\",\"about\":\"Ottawa's newest life drawing classes!\"}", … } ``` 3rd party reporting of same profile: ``` { "kind": 1984, "tags": [ [ "p", <pubkey>, "NS-nud,FA"] ], "content": "Lots of drawings of nude people", … } ``` Self-reporting of particular parts of a profile: ``` { "id": <eventId>, "pubkey": <pubkey>, "created_at": 1000000000, "kind": 0, "tags": [ ["t", "hastag"], ["content-warning", "I'm a trans pornstar. My avatar is G-rated, but the header pic is a bit racy. My website link goes to a porn site and most of my posts are porn-related.", "PN-trn,PN-trn-website,NS-ero-banner"] ], "content": "{\"name\":\"PollyPornstar\",\"about\":\"Award-winning trans pornstar\",\"banner\":\"https://somesite.com/somepic.jpg\",\"website\":\"https://pornsite.com\",\"picture\":\"https://somesite.com/anotherpic.jpg\"}", … } ``` 3rd party reporting of the same parts of the same profile: ``` { "kind": 1984, "tags": [ [ "p", <pubkey>, "PN-trn,PN-trn-website,NS-ero-banner"] ], "content": "Trans pornstar with racy banner and website link to a porn site.", ... } ``` ````