Unfortunately. I really wish $HOME was reserved for files I create myself. I know. I can create my own shit for that. But, I really wish every single random project I download to fuck around with didn’t drop a config directory or file in there. ITS MY HOME.
I mean, having config files in there makes a lot of sense. It allows you to move your home to some other machine/install and immediately feel at home, because everything is configured to your liking.
Now, the fact that many apps create their own directory instead of putting their stuff in ~/.config is pretty annoying.
Yeah. That’s more my frustration. That it’s implented poorly by most people. I don’t think that trying to change the standard by “adding another standard” would be helpful. Just minor frustration. Which usually leads me to putting all my organized directories and shit in a dedicated location. And I just let /home be the clutter that it is.
macOS by default makes /Users/* only readable by the owner, except for $HOME/Public, which is drwxr-xr-x, and $HOME/Public/Postbox, which is drwx-w--w-
700 cause I’m selfish.
700 is the only sane answer for directories inside
$HOME.Nah, there’s a lot of config files in there that other programs need to read.
Unfortunately. I really wish $HOME was reserved for files I create myself. I know. I can create my own shit for that. But, I really wish every single random project I download to fuck around with didn’t drop a config directory or file in there. ITS MY HOME.
I mean, having config files in there makes a lot of sense. It allows you to move your home to some other machine/install and immediately feel at home, because everything is configured to your liking.
Now, the fact that many apps create their own directory instead of putting their stuff in ~/.config is pretty annoying.
Also for multi user systems it’s handy that each user gets their own configs
Yeah. That’s more my frustration. That it’s implented poorly by most people. I don’t think that trying to change the standard by “adding another standard” would be helpful. Just minor frustration. Which usually leads me to putting all my organized directories and shit in a dedicated location. And I just let /home be the clutter that it is.
The programs usually run in user context and have access to the files.
Even if thinking very hard I cannot come up with a scenario where a program that does not run in user context needs access to user files.
macOS by default makes
/Users/*only readable by the owner, except for$HOME/Public, which isdrwxr-xr-x, and$HOME/Public/Postbox, which isdrwx-w--w-