fshy

Home / Storage

blossom.ditto.pub (Ditto Blossom server)

blossom.ditto.pubContent addressed blob serverstorage/blossom-ditto-pubJSONcomparereport an errorprovider JSON

Free allowance
No quota. Live server stats: 1,375,309 total blobs, 781.96 GB storage used, 8,684 uploads/24 h.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
anonymousno card, no phone
Binding limit
per-object-cap2 GB/upload
Evidence
reported2 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierNo quota. Live server stats: 1,375,309 total blobs, 781.96 GB storage used, 8,684 uploads/24 h. Max upload size 2 GB, max media size 1 GB, accepted types *.
unit GB; metered on stored-bytes
Pricenone stated
Limits
  • per-object-cap (binding) 2 GB/upload source
2 GB/upload, 1 GB for /media; images re-encoded to webp @192 by the server's media optimisation (so /media is lossy, but /upload of a raw blob is not)
Identityanonymous anonymous — Nostr keypair (BUD-11 auth token). No email.
Egressfree, unauthenticated GET by SHA-256
Per-object cap2 GB/upload (2000000000 bytes)
Retentionnot stated
Interfaceunknown Blossom / BUD-01 over HTTPS
ToolingBlossom clients, nostr SDKs, curl
Composes with2 GB per object makes it the best per-file ratio in the Blossom set; SHA-256 addressing composes directly with the chunk-and-replicate pattern.
ReliabilityOperator-run hobby infrastructure with ~782 GB on disk; a 500 GB deposit would double the server. No published retention, unlike 24242.io.
Parsed numbers
  • has-free-tier 1
  • per-object-cap 2 GB
Evidence 2
datesourcewhat it proved
2026-10-21blossom.ditto.pub/'1,375,309 Total Blobs / 781.96 GB Storage Used / 8,684 Uploads (24h)'; 'Max upload size 2 GB'; 'Authentication Required'; 'Accepted types *'
2026-10-21blossom.ditto.pub/uploadHEAD — 401, X-Reason: 'This needs a Nostr auth token (BUD-11)'
Unknown values 4
  • interface: the access interface was not established
  • per object cap notes: the field may be stated in a source that was not read
  • retention notes: the field may be stated in a source that was not read
  • retention stated: the field may be stated in a source that was not read