If the host you’re connecting to is already in your known_hosts, a malicious network can’t do anything but break the connection. If it tries to mitm the ssh connection, you’ll get the alert that’s someone could be “doing something nasty”.

Information leakage: Anything between you and the ssh server will be able to see that you’re connecting to a ssh server and how much data you transfer, but not what the data actually is.

I run used disks with tens of thousands of power on hours. Yes the risk of each disk dying is higher but only marginally and the cost is dramatically lower. To avoid data loss when they die, I have functioning backups. This system is working really well for me.

Huh good to know, thanks!

What’s the best way to make an offsite backup for 42tb at this point with 20mbps of bandwidth? It would take over 6 months to upload while maxing out my connection.

Maybe I could sneakernet an initial backup then incrementally replicate?

If you have a secure password Vaultwarden’s encryption will keep you safe until it’s broken by faster computers in the future or whatever.

SSDs have a write lifespan. Once you write ~400TB or whatever it’s rated for on a consumer SSD it dies. HDDs can take a lot more writes before dying.

Do you have an old computer that you can use as a server? If not, you could look for one used. Then get an 8TB disk and maybe a second one for backup if you want to store anything you can’t redownload.

some kind of api aggregator could probably work but i don’t think there is one yet