SocialJusticeHeals

@dan
If you do

./configure --prefix="$HOME" \
&& make && make test && make install

then you typically get ~/etc for the config files (and binaries in ~/bin)

~/.config is not part of any posix or Un*x standard I know of.

Some desktop environments do use it, but not because of any standard I am aware of.

@TheBaldness
For apps that Apple controls that may be fine, but most people do not get their apps from a single vendor and not all vendors are fast at pushing updates.

@TheBaldness
When you bundle everything for an app inside a self-contained directory, it's no different than static linking a binary.

An exploit in a library the package links against means that application is still vulnerable even if the same library on the operating system has been updated to fix the security flaw.

@TheBaldness
No. Static libraries are a security risk.
@wet_lettuce

@wet_lettuce
Should be /etc or /usr/local/etc or /opt/etc or /opt/vendor/product/etc or ~/etc.

With some exceptions for historic compatibility (like ~/.bashrc)

The man page should specify where.