laantungir/blossom
1
0
Fork 0
mirror of https://github.com/hzrd149/blossom.git synced 2025-12-08 14:58:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update 09.md

Browse Source
This commit is contained in:
k.
2025-01-04 19:01:39 +00:00
committed by GitHub
parent 8487a70a22
commit 52abe4467a
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
buds/09.md
View File

@@ -18,15 +18,16 @@ Example:
"kind": 1984,
"tags": [
["x", "<blob-sha256>", "<type-based-on-nip-56>"],
["x", "<another-blob-sha256>", "<type-based-on-nip-56>"]
],
"content": "<human readable report details>",
// other fields...
}
```
A report request may contain multiple `x` tags or contain some `p` or `e` tags which is not related to blossom server but is SHOULD be considered as a valid request.
The clients can include `e` or `p` tags to point to the event or the profile that contains this media if they want to make this report event useful for relays as well.
Server MUST respond to a report request with a success code or a code in 4xx/5xx range if there was any error.
Server MUST respond to a report request with a success code or a code in the 4xx/5xx range if there was any error.
### Client behavior
@@ -36,5 +37,5 @@ The clients can show a blob report button on posts or in blob details. Or its RE
The servers MAY keep the reports somewhere for operators to check and take action on them. they MAY use a list of trusted people or moderators to directly take action on blob without operator request.
Servers MAY consider removed blobs sha256 as blocked in order to prevent rewrite.
Servers MAY consider removed blobs sha256 as blocked to prevent rewrite.
Servers SHOULD advertise a route or landing page to provide their rules and term of service which affects the report process.