Blossom protocol
2025-07-26 11:55:09 +01:00 by Mark Smith
I‘m curious about this new protocol called Blossom.
They describe it as:
Blossom Drive: Store & Retrieve Data on Public Servers Using sha256 Universal ID
Which sounds kind of interesting, and also as:
Blobs served simply on media servers
Which I very much like the sound of.
For ages and ages I‘ve been wondering how I could use public/private key cryptography to improve how I publish my blog. It would be very cool if every piece of content could be verified so you knew for sure that I wrote it. That it wasn‘t intercepted mid flight and changed. Or that somebody isn‘t pretending to be me. I think that‘s what could be possible.
I‘m not a cryptography expert though. I know I could figure something out if I spent a bunch of time on it, but then in a few years time, I wouln't remember exactly how I had implemented it, and perhaps I introduced a bug (likely). It just sounds like a recipe for a lot of headaches. Everybody knows you shouldn‘t roll your own crypto.
But there aren‘t enough Blossom examples, or real world tutorials, for me to really fully understand how it could fit in with what I‘m doing. I‘m obviously missing something fundamental, I find the way it does authentication to be strange, compared to say authentication with Github or Stripe.
I have to use a Nostr event as authentication? What does that even mean?
Where will the files I upload get stored? On public server? Really? Who pays for it?
And what am I giving up? Am I then tied in some way to Nostr?
There are just too many unanswered questions for me to start a feature branch and try to integrate it into my workflow.
Having said all that, it would be awesome if all my blog posts were stored like that. #