blossom/buds/09.md

BUD-09

Blob Report

draft optional

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

PUT /report - reporting a media

The requests body MUST be a signed NIP-56 report event with x tags containing that hashes of the blobs being reported.

Example:

{
  "kind": 1984,
  "tags": [
    ["x", "<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.

Server MUST response to report request with a successful code or a code in 4xx/5xx range if there was any error.

Client behavior

The clients can show a blob report button on posts or in blob details. Or its RECOMMENDED to 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 blob 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 blob without operator request.

Servers MAY consider removed blobs sha256 as blocked in order to prevent rewrite. Servers SHOULD advertise a route or landing page to provide their rules and term of service which affects the report process.