PushOver support?

[JayBrown]

I'm using PushOver to send system/process infos & warnings from my servers & clients to my main macOS client including my iPhone. It would be nice (at least for me 😉) to have support for PushOver too. The only issue might be that the warning messages' lengths might exceed the PushOver limits. (But I currently can't say what restrictions are in place.)

[joergschultzelutter]

The various message formats and lengths are actually one of the reasons why this software uses custom-tailored API / mail access for each target platform (mail / DAPNET / Telegram).

There is still hope for you 😉. I am on the verge of finalizing the work on an APRS plugin for the Apprise multi-messenger platform. That plugin in question will allow users to send messages via ham radio (APRS) and is basically a clone of my DAPNET plugin for apprise - which is something that I always wanted to add to this software.

Once my work on the plugin has been merged with Apprise's master branch, I plan on integrating Apprise with mowas-pwb. And once that is done, the number of supported messengers would literally be limitless (yes, Apprise supports PushOver, too).

There might be one potential downside: I probably cannot custom-tailor the outgoing message on a per-messenger-type - which means that messages generated via Apprise might have a "poorer" look-and-feel / message lengths in comparison to the currently implemented native message formats. I do plan to introduce the Apprise interface as additional option - which means that the current communication channel formats will stay "as is".

I'll update this issue once the integration is complete, ok? :-)

[JayBrown]

This is perfect. Thank you for the info! 👍 I was basically just looking for a way to get emergency notifications on my Mac clients, because I often just switch off my phone. And since I like CLIs & shell scripting, this looked like a really good option. Thank you for your work!

[joergschultzelutter]

Brief update: I finalized the work on the Apprise plugin; my PR is currently getting reviewed by the author. Once that PR has been approved, I intend to add the following changes to mowas-pwb in the next weeks:

1) Generic Apprise support (which will then resolve your issue ticket). Note that I will implement the usage for TWO Apprise config files. Reason - see (2) 2) an experimental feature for those who intend to use any of the two Apprise config files. Usually, the original government texts are very very VERY long and I want/need to shorten them in case the text is sent to mobile/pager devices. So what I intend to do is the following:

a) Apprise config file A receives the text "as is" and is supposed to target messengers like Telegram, PushOver, .... b) Apprise config file B will receive an abbreviated text version. mowas-pwb will enable the user to specify an external services URL (potentially, ChatGTP or Google Bard) which will abbreviate the text in a proper sense. As a fallback / alternative option, a pure offline text summarizer service can be used.

Unfortunately, the current version of Apprise does not allow me to specify different texts for various plugins - e.g. both Telegram and a SMS service will receive the same input. Therefore, the usage of two config files acts as a workaround.

Stay tuned ....

[joergschultzelutter]

Future coverage per branch https://github.com/joergschultzelutter/mowas-pwb/tree/apprise

[joergschultzelutter]

Code migration to Apprise API complete. Have deprecated native Telegram / DAPNET implementations in favor of Apprise API.

Pending: Code refactoring, text summarizer implementation

[joergschultzelutter]

Release 1.0.0 deployed