Awesome work, this is great! It seems like I have to write notification code for every little project I build.
One that'd be interesting would be to have an Apprise "server" where all config lives, and a client that receives commands. This way, a single Apprise installation could service multiple hosts without having to duplicate configuration files.
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 :).
One that'd be interesting would be to have an Apprise "server" where all config lives, and a client that receives commands. This way, a single Apprise installation could service multiple hosts without having to duplicate configuration files.