Apprise: Open-Source, Self-Hosted, Push Notifications | Hacker News Reader

Apprise: Open-Source, Self-Hosted, Push Notifications

github.com

114 pointsthunderbong14 comments

How does it work, does it still use Firebase Cloud Messaging and Apple Push Notification Service underneath?

Yes, it does:

https://github.com/caronc/apprise/wiki/Notify_fcm

In case it's not clear: it's not only for iOS/Android push notifications. It provides a single API to send notifications via a whole bunch of channels (Slack, Telegram etc.).

e.g. I have some code that notifies me in Telegram when something happens. I had to integrate with the Telegram API to do that. That's easy, but what if I want to switch the notification to Slack or something? Or send it to to multiple destinations? My code gets messy pretty quickly. If I switch to using this, I can have multiple scripts that all use the same API, and the choice of destination(s) become some small amount of config in each script.

Fantastic project, I use it with ntfy.sh and it really makes things easier.

I wish it supported Jami messages though, but Jami is somewhat hard to do programmatically on Ubuntu, the DBus doesn't seem to cross between Snaps.

what's the usecase for combining this with ntfy?

Ntfy is a notification service. Ntfy is 1 of the 100+ notification services Apprise supports. Apprise is basically a switchboard for notifications; a one stop shop.

Specifically, ntfy.sh sends to Ntfy's mobile app or to their web notifications page, and you don't need an API key just an arbitrary secret channel name.

This is an amazing product. Great job.

This looks great! I'm assuming that web push notifications (https://web.dev/explore/notifications) exist somewhere in the docs but I can't find them.

Support for every push service except APNS???

I guess the idea is to use FCS instead (which can push to APNS) but I also found it odd that it was missing.

Too bad about the Linux dependency.

This would be a nice API to have on simple MCUs.

what is going on with those Dockerfiles?

They're just used to test different Python environments with. 2 of them for RPM building and testing in RHEL 8 & 9.

They all play a roll with merge requests during (GiHub Actions) pipeline testing and code coverage.

Reply on news.ycombinator.com