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.
Usually, but there might be services running as other users that reference those configs. It really just depends on what’s on your system. Obviously you can make 700 work, but it might require tweaking some stuff.
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.
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.
Usually, but there might be services running as other users that reference those configs. It really just depends on what’s on your system. Obviously you can make 700 work, but it might require tweaking some stuff.
Yes, this is what I wonder.
I use Linux since ca. 2005 and never ever had a program not working because it could not read a user’s
$HOMEcontents.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-I gotta ask why they put Public in home
Because it’s a user-specific folder that says “This is mine, but you can see it.”