I finally forced myself to go over [Storej's white paper](https://www.storj.io/documents/storj-sustainability-whitepaper.pdf) to understand how they're achieving such a high level of availability using just consumer-grade hard drives scattered across people's living rooms. It all boils down to [Reed–Solomon erasure coding](https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction). You distribute 80 chunks, but in reality you only need 29 to reconstruct the complete data. It would be amazing to have the same or similar error correction implemented into Blossom.
I could see scenarios where I would happily offer 30GB of data storage on my blossom server to have 10GB of distributed, reliable and resilient data across multiple blossom servers.
nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpr3mhxue69uhhxct5v4kxc6t5v5hxs7njvscngwfwvdhk6tcpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsk7wj75 do you think we can have something like that in blossom soon or are there pitfalls I didn't considered?
It probably wouldn't be difficult to build something like storej on top of blossom and even use the same chunking and encryption methods. however I don't think it makes sense for blossom to support chunking and distributed storage directly
blossom is good at transferring and replicating smaller files around the internet.
that said, the idea of offering some of your free storage to backup other users (public) data is a great idea and something every distributed storage solution to date has been trying to solve in one way or another.
But none of them had the nostr social graph... 😁
