P2P proves yet again to be the best solution for availability problems. At least until the seeds disappear, which happens because storage isn't infinite.

[–] uuj8za@piefed.social 2 points 13 hours ago (1 children)

At least until the seeds disappear ... storage isn’t infinite.

Which is why Radicle is kinda interesting... it seems like it may be kind of easy to have lots of different seeds in different places. I'm currently using radicle.garden as my main always-on seed. If they start having issues, I could self-host. If I start having issues, other randos also run Radicle seed servers. Someone who wants to download my project could use any one of these seeds and be guaranteed to get a legit version of the project.

If fact, it seems like the user doesn't even have to care about where the code is hosted at all. A radicle clone looks like this:

# Clones a git repo.
rad clone rad:z3WukSjzicL8WaZHFALbBwb2r8W52

There's no indication of which servers to check. It just checks the "Radicle network" and clones from a random seed?? (I think?)

Smaller projects will have way less seeds, but if you use that project, you could contribute to their availability by seeding! You make a copy for yourself to keep your build going and you also help the rest of the network?!

(Again, juuust started looking into this, but it seems cool so far!)

[–] ICastFist@programming.dev 1 points 7 hours ago

My worry was less with servers and more with interest, much like how some torrents are dead because there are zero seeds. I suppose the author of projects might remain as the sole seed for a longer period than the mirror seeds, but there are many that can be abandoned by the single dev for whatever reason