can you elaborate on IPFS brokenness? out of interest
When I first started with Nostr back in 2023, IPFS sounded like a perfect match. But the more I played with it, the more convinced I became that IPFS is a broken and failed project. Nostr needs something simpler and more straightforward—and then nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpr3mhxue69uhhxct5v4kxc6t5v5hxs7njvscngwfwvdhk6tcpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsk7wj75's Blossom came.
Ever since then, I've been dreaming about redundant decentralized storage with file fragmentation—something like what StorJ describes in their white paper:
"All data is encrypted and sharded using Reed Solomon erasure coding. The resulting pieces are distributed around the world. A typical large file is divided into 64 MB encrypted segments, and each encrypted segment is divided into 80 erasure-coded pieces—any 29 of these are sufficient to reconstruct the original file. Each of these 80 pieces is stored on a different drive globally, spread across diverse geographies, operators, power supplies, and networks."
In Blossom, this would be a killer feature. You would offer space on your server to others, and in exchange, get redundancy for your own files, or you would simply pay for it. File metadata could be published as a specific kind hosted by relays.
Discussion
I'm not op, but fiatjaf has posted this in one of the comments in this chain.
It is almost impossible to get content synced over the network. Try to sync a simple picture from your home node to a node in your laptop when you are on different networks... It will take hours or it will never happen.
I mean what I said was just getting content from well connected gateways anyway, or uploading to one, like nostr client providers can have their own default gateways and etc. i wasnt talking about p2p ipfs experience.
anyway I checked blossom, (first time hearing about it).
seems similar to what i was thinking with ipfs.
but instead its a cdn protocol basically, i think. didnt deep dive in it yet.
so i believe its like a normal cdn but hash based and has a known format, endpoints. so you can extract the hash (like i said in ipfs). and then check other blossom compatible cdns.
and of course user can give list of blossom cdns on their profile as well.
tbh blossom looks more lightweight and easier to implement for already existing cdn solutions. i see no problems with it.
seems like a more lightweight solution. i liked it.
i still see no problem with supporting both or more. similarly you can share a media with a https ipfs gateway URL, so it works everywhere.
and then while viewing extract the hash and check multiple other gateways with that hash as well using HEAD method.
which would also make those gateways search for the content. distributing the GET traffic more later when more users ask for same thing.
but yeah blossom looks nice, maybe better.