Blossom Server joins the registry

Blossom Server is a Nostr-authenticated blob storage server. Clients upload files and retrieve them by SHA-256 hash, with retention governed by configurable MIME-type rules. Authentication is via Nostr-signed events (kind 24242); no traditional user accounts. Includes a built-in admin dashboard for managing blobs, users, and reports.

upstream → website → package → MIT

• 6.4.1:22026-10-22Stops trusting certificates from a compromised certificate authority (eMudhra).
• 6.4.1:12026-10-10Requires StartOS 0.4.0.2. A brief network outage does not add Set Public Domain to the service's tasks when the public domain is the server's .local address.
• 6.4.1:02026-10-10Updates Blossom Server to 6.4.1. Stored web pages are downloaded instead of displayed, and uploads and deletes must be signed for the exact file.
• 6.4.0:22026-10-10If the public address goes missing, Blossom keeps running and shows a Set Public Domain reminder, which clears itself once the address is back. New installs choose the .local address as their public domain.
• 6.4.0:12026-10-02Disable Private Mode opens uploads to every Nostr key and keeps your allowlist, and retention periods apply to every file, whoever uploaded it. If your server had Private Mode off with keys still on its allowlist, this update turns Private Mode on; run Disable Private Mode to open it.
• 6.4.0:02026-10-01Updates Blossom Server to 6.4.0. With Private Mode off, visitors can upload from the landing page without a Nostr key of their own; the landing page and admin dashboard serve their styles from your server, and mirroring from private network addresses is refused.
• 6.3.1:02026-09-19Update to Blossom Server 6.3.1: large duplicate re-uploads now reliably receive their success response, and range requests that extend past the end of a blob are clamped instead of failing with error 416.