rather seed things with fewer seeds and which are about to die.
If you want 90% of the stuff indexed on pirate sites is dead or with only 1 seed, I haven’t found tools that take it automatically.
But there is this initiatives for books, books or paid courses are more subject to copyright strikes than entertainment material, therefore more difficult for students or workers to find.
charitable_seeding_for_nonprofit_scientific_torrents
library_genesis_project_update_25_million_books
libgen also uses IPFS and seems much better for this purpose.
I used to just seed Epic exclusives. Now there aren’t any Epic exclusives*. Coincidence? I think not.
*Other than Kingdom Hearts grrr
You could install a tor relay or i2p
my dream is to build my own NAS. it would handle everything i need: it would be a Nextcloud, media server, website host, Matrix server, Minecraft server, and when i’m not doing anything with it at the moment i’ll have it donate its time to seeding and relaying
if your that passionate about NASs, may I ask how does one negate data loss if a lighting were to strike? or fire?
I get Raid an all that, but I don’t care how many times my data got burnt if it ever will.
Same with lightning, lightning rods are a thing, so maybe that? Idk what would be dmged if an entire lightning passes thru your house in a wire or not, like electromagnetic fields are a thing.
I suppose remote backup is the only option for something that destroys everything in the area, but raid is essential anyway.
Off-site backup is the proper answer to your question. All this really depends on your own tolerance or comfort with the possibility of losing data. The rule of thumb is that there should be at least three different copies of your data, each in a different physical location. For each of them, there should be redundancy of some kind implemented to guard against hardware failure. Redundancy is typically achieved by using mirrored drives or by using RAID of some kind. Also, if you’d like to know, using RAID in which you can only lose one disk in the array is not typically considered a sufficient level of protection because of the possibility of a cascading drive failure during replacement of a failed disk. It should be at least two.
i’ll have to look more into that. the obvious answer is “keep it off site”, but that only applies if you’re doing backups. if it’s a NAS with several different purposes like the one i want, i’m not actually sure. i’ll keep reading about it
I sometimes do the same when I spot something new and high demand
Doing the Lord’s work. Godspeed.
