> First thing to do, is to create a new "homedir" inside the OS-provided homedir. I want my homedir to be immediately backup-able, and unfortunately most OSs sp

> First thing to do, is to create a new "homedir" inside the OS-provided homedir. I want my homedir to be immediately backup-able, and unfortunately most OSs spam the system homedir with various nonsense, e.g. applications (on Mac, Chrome installs (or used to) in `~/.ApplicationData`, on Linux, there's various package managers' binary caches, ...). I used to name this `home` but next time I'll name it `my`, less confusing. What's really bullshit about this is the mixing of crap you wouldn't want to back up and actual user-relevant documents and config. The lowest-friction use of a bunch of programs will end up putting config you might want to keep, or documents, in your actual '~/' (say, "~/Documents"), but as you point out tons of stuff that you don't want ends up in there, too. At this point we almost need two "home" environment variables on unixy systems (and Windows has the same problem, of course). Another issue that's mostly Linux-specific (maybe the BSDs, too?) is the way someone who's not even that into sysadmin junk may end up with a few files in '/etc' that they'd like to back up, when really those aren't intended for use by any other users on the system (of which there may well be no other human ones) and could go in the home dir or somewhere else segregated from package-manager-sprayed, untouched-by-the-user noise.