Oddbean

Just to understand how blossom works... it's the same image because you uploaded it before by yourself on your server? Or it's because I uploaded it on mine and the image has been replicated on yours? I thought we have to add blossom servers into our blossom-drive account to allow file to be served by several blossom-servers :D

I just re-uploaded it to my server, but its the same sha256 hash so if it ever gets removed from your server it can still be found on my server There isn't any replication yet. but in the future my server could automatically download and host your blobs if I was following you 😀

Thanks for your explanation :) For the test I deleted the image from my blossom drive. Do we need to keep the blob to allow the file to be retrieved in your server? Or the simple fact to upload once a file on a blossom server (+ to be hosted on another blossom server) is enough to keep the file indefinitely? If all the blossom servers delete the file, does the file become unreachable? Will write on a tutorial on blossom I need to understand what I'll say 😅

If you delete the file from your server it wont be accessible on your server anymore, however because I uploaded it to mine it will still be accessible if people load it from cdn.hzrd149.com similar to nostr relays, blossom servers aren't aware of other servers and don't have any p2p communication. however there is nothing stopping them from talking p2p, but that code (and protocol) hasn't been written yet But we don't necessarily need p2p communication for censorship resistance. user can publish a k:10063 event that advertises where other users can easily find your blobs. So if you find that one server has gone down or is censoring you. you can transfer or re-upload your blobs to a new server, then update your k:10063 event to let other users you have moved https://github.com/hzrd149/blossom/blob/master/Nostr.md#user-server-discovery