Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ntfy – open-source Push to Mobile

ntfy.sh

Post reply on HN
Print view View original

31–40 of 53 posts

Re: Ntfy – open-source Push to Mobile

#32

Post by crtasm »

rahimnathwani wrote: post #17
kayson wrote: post #10

I've been using Gotify [1] for a very long time and have been quite happy with it. Basically no impact on battery life. For devs - there are mature libraries like shoutrr [2] and apprise [3] that let you support multiple notification systems with no extra work. 1. https://gotify.net/ 2. https://shoutrrr.nickfedor.com/v0.17.0/ 3. https://github.com/caronc/apprise

Right, but if you use ntfy.sh you can get proper mobile push notifications (instead of keeping the app running and using long polling or websockets). If you use the public version of ntfy.sh then you don't need to do anything to set this up. If you self-host, you need your own Firebase Cloud Messaging (FCM) account and (for iOS) your own Apple Developer account so you can use APN.

Also the docs point out >Using Firebase is optional and only works if you modify and build your own Android .apk. For a self-hosted instance, it's easier to just not bother with FCM.

https://docs.ntfy.sh/config/#firebase-fcm

Re: Ntfy – open-source Push to Mobile

#33

Post by oulipo »

rahimnathwani wrote: post #21
oulipo wrote: post #20

Earlier quoted context omitted.

Personally I use FCM (Firebase push notifications) with a Capacitor plugin for push notifications, it works decently

I didn't know what you meant by Capacitor, but I now understand it's a modern replacement for Apache Cordova: https://capacitorjs.com/

Yes exactly, it's an easy way to build a web-based app and run it on iOS and Android, accessing the native API through a javascript bridge. There's also NativeScript in that space

Re: Ntfy – open-source Push to Mobile

#37

Post by robgibbons »

Superbowl5889 wrote: post #5

I wonder whats the difference between permisions do giant apps like whatsapp, instagram have for notification service. cause they seem like perfectly integrated themselves into this, while ntfy has to pose itself as battery consuming application I'm planning to using ntfy for notifications like bitwarden vault backups, if apps are updated.

FCM (Firebase Cloud Messaging), and Apple's own APN (Apple Push Notifications) work as a single OS level service, and they are multiplexed so that many different apps can route through them with a single connection, even waking your phone/watch from sleep. There are open/de-Googled alternatives like UnifiedPush, but they're not integrated at the OS layer (they run as a background worker thread), and can't match the battery efficiency or sleep-wake capabilities of those built into the OS/low-level networking layer.

Re: Ntfy – open-source Push to Mobile

#38

Post by sixothree »

lxgr wrote: post #13
sixothree wrote: post #12

Earlier quoted context omitted.

Incredibly useful to give any app the ability to send you a notification with a single line of code or shell. Only one minor caveat for self-hosted iOS users - content of the messages come from your server, but the trigger still comes from ntfy.sh server.

You can "install" the PWA on iOS by adding it to your home screen, then your ntfy instance can use APNs directly (via Web Push)!

Very nice. Thank you. I am not super concerned but I know people here tend to be.

Re: Ntfy – open-source Push to Mobile

#40

Post by loremm »

dewey wrote: post #22
oulipo wrote: post #18

Earlier quoted context omitted.

What's the advantage over, say, having a Telegram bot push you messages instead of notifications?

The advantage is that I don’t have to use Telegram and Pushover can just be triggered by curl in any scripts I use.

Not nitpicking but I have curl send telegram, it's not bad but I agree pushover looks nice

I have it so it can send email, telegram, or twilio call depending on urgency

Post reply on HN