[l2g]

Hmm... I don't know if I'd want the headache of having everyone's passwords, tokens and API keys on a server I managed and deal with the privacy that goes with it...

But I was thinking of still supporting YAML or JSON formatted files to which users could protect with permissions and store their personal data there instead of being visible on the command line. the url would be something like file://path/to/config.yaml or http://localserver/path/to/config.yaml. So in a way, this kinda/sorta fits with your idea too :).

Thanks for your positive feedback!

[cmer]

I meant a self-hosted server, and self-hosted client.