The list of blossom server implementations is slowly growing, we have six so far 😀
Discussion
The real nostr 2.0
Isn’t Blossom just an NIP for how to manage media endpoints? How is it different from the “media metadata” NIPs?
Yeah, it is, I'm mostly kidding. It just looks like nostr 2.0 because it has a similar but separate network architecture and content discovery mechanism.
It's different from NIP 96 in that it's simpler and more focused on discovering verifiable file contents based on the file's hash, whereas it's unclear to me how strong the guarantee is with NIP 96 that you can verify a file hasn't changed, since the spec says:
> Note that the "
This could probably all be fixed within NIP 96 itself, but hzrd and stu have decided to go in a different direction.
Nostr 2.0 is dead. Posting Merkle roots on-chain all the time was just too expensive.
Merkle tree-based file storage on #Nostr relays is still coming though, because files should be chunked in decentralized networks.
I think you’ll love what we’ve done with Negentropy too! Changed the name FOREST to LeafSync as well, found a way to blend it with Negentropy.
It’ll be unfolding soon.🍻
Did you name it blossom just so there could be awesome blossom? That name is immaculate.
I still don't understand how it works and why I should use it.
🔥
Wen blossom section on nostr.watch nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx
