Hacker News Reader

In the config.rc file you could call that folder however you want.

I personally do not like ".meta", because it is not clear what kind of information it may contain. "Meta" might be anything, documentation, description, website, design papers, everything is meta. It is a bit like using "Information" as a menu entry for a website.

It sounds like we should probably all get together and write a draft RFC for this. Choosing a good directory to toss everything into would be grand.

I'd prefer .well-known since there's already an RFC for it, but maybe .dev-extra would be more appropriate?

Do you really want to type either of those prefixes thousands of times? Brevity and lack of special chars in the name would be nice to have.

`.config` is probably a decent choice, as ~/.config for per-user settings seems to be gradually gaining adoption.

Or .well-known? (analogous to https://tools.ietf.org/html/rfc5785)