Problem with data persistence: people die. Someone could be hosting something in some way, and if they die then their whole thing will be gone in one week to two years. MEGA / Google Drive / whatever cloud storage will delete all of their stuff due to inactivity. If they host a multi-terabyte website, that will disappear if they die; when will that happen after they die? Depends on what arrangements they had set up. Not everyone dies of old age. Some get unlucky or die young for whatever reason like being reckless or getting addicted to something.

Background/ignore:
I was thinking about this because today I learned that "video game challenge" YouTuber Mitten Squad died at age 27: https://iv.ggtyler.dev/watch?v=lol5wIVUOtI "Mittensquad Has Passed Away.. (not joking)". (YT ID starts with "lol". When this guy was still alive I watched his Fallout and Halo videogame videos. Maybe he drank himself to death. His video on controlling Fallout 3 with his eyes was interesting.)

>>10267
Public key authentication so you don't have to enter a password each time:
>computer1$ # # https://iv.ggtyler.dev/watch?v=33dEcCKGBO4
>computer1$ # cd ~/.ssh; l # backup any files that exist in here
>computer1$ # ssh-keygen -b 4096 # press enter, don't show private key to anyone
>computer1$ # ssh-copy-id [email protected] # copy public key (*.pub) to other computer
>computer1$ # ssh [email protected] # added ~/.ssh/authorized_keys
If you still have to enter a password, then do it again but with "ssh-keygen -t ed25519"; otherwise:
>computer1$ # chmod 755 authorized_keys # 700 is better if that works
>computer1$ # ssh -v [email protected] # =...debug1: send_pubkey_test: no mutual signature algorithm
Perhaps use "ssh-keygen -t ed25519" to begin with and not "ssh-keygen -b 4096" which I thinks makes a crappy RSA key. As of 2024 Ron-Someone Algorithm = "cryptographically weak". (Also, queue keygen music.)