I've been playing with ntfy as a replacement for Pushover and have worked out a configuration for AITOOL. I've used Pushover for years and have been happy with it, but it won't run on GrapheneOS without Google services installed. Pushover and ntfy do about the same thing, but in different ways and with different feature sets. One feature that I have found useful in ntfy is the ability to push messages to a web browser as well as a phone. New images are pushed to the browser in real time, and optionally the browser will make a sound when a new image arrives.
ntfy works on the Pub/Sub model. A topic is defined and devices can subscribe to the topic. When a message is published to the topic then any device subscribed to that topic will see the message. Kind of like a group chat. So if the ntfy phone App and a web browser are both subscribed to the same topic, then any messages published to that topic will be delivered to both devices. In the above image I have obscured the topic name since anybody with that name could view and publish on my account. Therefore topics should be created wisely. Make them longer and more complex for greater security. Just like passwords.
AITOOL has native support for Pushover and Telegram, but curl is used to send with ntfy. Here's the config that I'm currently using.
The full Params line is:
-H "Authorization: Bearer tk_ob93rvkfhieftunhjolkwtklpwvxe" -T "C:\StoredAlerts\[ImageFilename]" ntfy.sh/MySecretTopic
This is for a paid ntfy account. If a free account is being used then the line would look like this:
-T "C:\StoredAlerts\[ImageFilename]" ntfy.sh/MySecretTopic
The long ugly code is representative of a token that a paid subscriber would receive. Free accounts are throttled and are limited to 2MB file attachments. Depending on the use case a free account might work fine, but while testing I exceeded the limits of a free account.
While testing I found that AITOOL needs to be run as an administrator to run curl correctly.
ntfy is open source and can be self-hosted. One negative aspect of ntfy is that the Android App is well done, but the IOS App is not. I've not seen the IOS App. I'm just going by what the developer said in an interview. Here's the interview.
Pushing ntfy to the next level with Philipp C. Heckel (Changelog Interviews #562)