[HN Gopher] Apprise: Open-Source, Self-Hosted, Push Notifications
___________________________________________________________________
Apprise: Open-Source, Self-Hosted, Push Notifications
Author : thunderbong
Score : 78 points
Date : 2024-02-01 13:35 UTC (9 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| eternityforest wrote:
| 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.
| ranger_danger wrote:
| what's the usecase for combining this with ntfy?
| l2g wrote:
| 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.
| satvikpendem wrote:
| How does it work, does it still use Firebase Cloud Messaging and
| Apple Push Notification Service underneath?
| moehm wrote:
| Yes, it does:
|
| https://github.com/caronc/apprise/wiki/Notify_fcm
| rahimnathwani wrote:
| 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.
| testernews wrote:
| Support for every push service except APNS???
___________________________________________________________________
(page generated 2024-02-01 23:01 UTC)