Mirror/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-01-31 10:31:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

more details.

Browse Source
This commit is contained in:
Kay 2025-01-03 20:05:59 +00:00
parent 8c85a2f913
commit c63a784de7
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
56.md
View File

@ -22,7 +22,7 @@ are reporting.
If reporting a note, an `e` tag MUST also be included referencing the note id. If reporting a note, an `e` tag MUST also be included referencing the note id.
A `report type` string MUST be included as the 3rd entry to the `e`, `p` or `x` (SHOULD be info hash of a blob which is intended to be report) tag A `report type` string MUST be included as the 3rd entry to the `e`, `p` or `x` tag
being reported, which consists of the following report types: being reported, which consists of the following report types:
- `nudity` - depictions of nudity, porn, etc. - `nudity` - depictions of nudity, porn, etc.
@ -33,7 +33,9 @@ being reported, which consists of the following report types:
- `impersonation` - someone pretending to be someone else - `impersonation` - someone pretending to be someone else
- `other` - for reports that don't fit in the above categories - `other` - for reports that don't fit in the above categories
Some report tags only make sense for profile reports, such as `impersonation` Some report tags only make sense for profile reports, such as `impersonation`.
- `x` tags SHOULD be info hash of a blob which is intended to be report. when the `x` tag is represented client MUST include an `e` tag which is the id of the event that contains the mentioned blob. also, additionally these events can contain a `server` tag to point to media servers which may contain the mentioned media.
`l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) to support `l` and `L` tags MAY be also be used as defined in [NIP-32](32.md) to support
further qualification and querying. further qualification and querying.
@ -81,7 +83,9 @@ Example events
{ {
"kind": 1984, "kind": 1984,
"tags": [ "tags": [
["x", "<blob hash>", "malware"] ["x", "<blob hash>", "malware"],
["e", "<event id which contains the blob on x tag>", "malware"],
["server", "https://you-may-find-the-blob-here.com"]
], ],
"content": "This file contains malware software in it.", "content": "This file contains malware software in it.",
// other fields... // other fields...