laantungir
/
blossom
mirror of https://github.com/hzrd149/blossom.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

bud-07: media report.

This commit is contained in:
Kay 2025-01-02 11:13:28 +00:00
parent 995f715c96
commit 29cbfbf504
2 changed files with 44 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
buds/01.md
View File

@ -26,7 +26,7 @@ Authorization events are used to identify the users to the server
Authorization events must be generic and must NOT be scoped to specific servers. This allows pubkeys to sign a single event and interact the same way with multiple servers.
Events MUST be kind `24242` and have a `t` tag with a verb of `get`, `upload`, `list`, or `delete`
Events MUST be kind `24242` and have a `t` tag with a verb of `get`, `upload`, `list`, `report`, or `delete`
Events MUST have the `content` set to a human readable string explaining to the user what the events inteded use is. For example `Upload Blob`, `Delete dog-picture.png`, `List Images`, etc

43
buds/07.md Normal file
View File

@ -0,0 +1,43 @@
# BUD-07
## Media Report
`draft` `optional`
This bud defines a new endpoint for clients and users to report medias to servers.
### PUT /report/<sha256> - reporting a media
Client MUST provide a report json according to the [NIP-56](https://github.com/nostr-protocol/nips/blob/master/56.md) in the request body.
Example:
```json
{
"kind": 1984,
"tags": [
["x", "<media-sha256>", "<type-based-on-nip-56>"],
],
"content": "<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.
Server MUST response to report request with a successful code or a code in 4xx/5xx range if there was any error.
> Note: servers may requests for authorization with `t` tag of `report` as per [BUD-01](./01.md).
### Client behavior
The clients can show a media report button on posts or in media details. Or they merge this with normal nostr report and send it to both relays and blossom server. other clients can receive it from relays and hide or blur reported medias from trusted friends.
### Server behavior
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 media without operator request.
Servers MAY consider removed medias sha256 as blocked in order to prevent rewrite.
Servers MAY advertise a route or landing page to provide their rules and term of service which affects the report process.