blossom/buds/07.md

BUD-07

Media Report

draft optional

This bud defines a new endpoint for clients and users to report medias to servers.

PUT /report/ - reporting a media

Client MUST provide a report json according to the NIP-56 in the request body.

Example:

{
  "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.

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.