laantungir/blossom

mirror of https://github.com/hzrd149/blossom.git synced 2026-07-22 07:48:28 +00:00

Go to file

hzrd149 2c30864340 BUD-00: allow BUDs to define client-side conventions

The definition restricted BUDs to features a server implements, but
BUD-10 (the blossom: URI schema) is already a client-side convention.
Broaden the definition to cover client-side conventions and data
formats built on Blossom blobs that servers do not implement.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-15 11:03:49 -05:00

BUD-00: allow BUDs to define client-side conventions

2026-06-15 11:03:49 -05:00

implementations

Fix links to buds folder

2026-02-02 15:11:50 -03:00

LICENSE.txt

add public domain license

2024-04-12 15:41:53 -05:00

README.md

Move HEAD /upload back into BUD-06

2026-04-16 10:36:39 -05:00

README.md

🌸 Blossom - Blobs stored simply on mediaservers

Blossom uses nostr public / private keys for users identities.

What is it?

Blossom is a specification for a set of HTTP endpoints that allow users to store blobs of data on publicly accessible servers

What are blobs

Blobs are packs of binary data addressed by their sha256 hash

Protocol specification (BUDs)

BUDs or Blossom Upgrade Documents are short documents that outline an additional feature that a blossom server may implement.

BUDs

Endpoints

Blossom Servers expose a few endpoints for managing blobs

GET /<sha256> (optional file .ext) BUD-01
HEAD /<sha256> (optional file .ext) BUD-01
PUT /upload BUD-02
HEAD /upload BUD-06
GET /list/<pubkey> BUD-12 (unrecommended)
DELETE /<sha256> BUD-12
PUT /mirror BUD-04
HEAD /media BUD-05
PUT /media BUD-05
PUT /report BUD-09

Event kinds

kind	description	BUD
`24242`	Authorization token	11
`10063`	User Server List	03

License

Public domain.