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

21–30 of 53 posts

Re: Ntfy – open-source Push to Mobile

#21

Post by rahimnathwani »

oulipo wrote: post #20
rahimnathwani wrote: post #17

Earlier quoted context omitted.

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.

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/

Re: Ntfy – open-source Push to Mobile

#22

Post by dewey »

oulipo wrote: post #18
dewey wrote: post #14

Not Open Source but I’ve been using https://pushover.net/ for this use case since forever. The website still looks the same as on the day I signed up for it probably more than 10 years ago. Never had an issue and using that in all my scripts or cron jobs.

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.

Re: Ntfy – open-source Push to Mobile

#23

Post by mbirth »

oulipo wrote: post #18
dewey wrote: post #14

Not Open Source but I’ve been using https://pushover.net/ for this use case since forever. The website still looks the same as on the day I signed up for it probably more than 10 years ago. Never had an issue and using that in all my scripts or cron jobs.

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

Notifications can carry metadata like specific alert sounds or priorities. High priorities will even break through silence modes of your phone.

And you get a nice client with icons for each notification source, can filter by them, etc.

Re: Ntfy – open-source Push to Mobile

#24

Post by crtasm »

lone-cloud wrote: post #8

I'm a privacy focused self hoster and ntfy was not good enough for me so I created Prism with an optional Android app: https://git.lonecloud.dev/lone-cloud/prism The difference: Your phone doesn't get notifications from your notification service directly, but from Mozilla which helps to hide your digital fingerprint of you using a separate notification provider like ntfy. Prism also allows Telegram or Signal to act a…

Interesting, how is it able to send via Mozilla? I did a quick search in the repo and the term isn't found.

Re: Ntfy – open-source Push to Mobile

#25

Post by grapemane »

lone-cloud wrote: post #8

I'm a privacy focused self hoster and ntfy was not good enough for me so I created Prism with an optional Android app: https://git.lonecloud.dev/lone-cloud/prism The difference: Your phone doesn't get notifications from your notification service directly, but from Mozilla which helps to hide your digital fingerprint of you using a separate notification provider like ntfy. Prism also allows Telegram or Signal to act a…

In what ways is your digital fingerprint being monitored where your notification providers are being captured?

Re: Ntfy – open-source Push to Mobile

#26

Post by lone-cloud »

crtasm wrote: post #24
lone-cloud wrote: post #8

I'm a privacy focused self hoster and ntfy was not good enough for me so I created Prism with an optional Android app: https://git.lonecloud.dev/lone-cloud/prism The difference: Your phone doesn't get notifications from your notification service directly, but from Mozilla which helps to hide your digital fingerprint of you using a separate notification provider like ntfy. Prism also allows Telegram or Signal to act a…

Interesting, how is it able to send via Mozilla? I did a quick search in the repo and the term isn't found.

The webpush endpoint registration is initiated from the client. The Android app can act as a client and it's the one that registers Mozilla's autopush service.

Re: Ntfy – open-source Push to Mobile

#27

Post by lone-cloud »

grapemane wrote: post #25
lone-cloud wrote: post #8

I'm a privacy focused self hoster and ntfy was not good enough for me so I created Prism with an optional Android app: https://git.lonecloud.dev/lone-cloud/prism The difference: Your phone doesn't get notifications from your notification service directly, but from Mozilla which helps to hide your digital fingerprint of you using a separate notification provider like ntfy. Prism also allows Telegram or Signal to act a…

In what ways is your digital fingerprint being monitored where your notification providers are being captured?

I meant that at the network level, should something be monitoring, your client would be making requests to a unique (ntfy) address that virtually nobody else ever uses. Requests to Mozilla are more crowd blended as it's quite popular already.

Re: Ntfy – open-source Push to Mobile

#28

Post by subscribed »

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.

Publicly hosted version is nearly useless if you'd like to use it to send notifications from your tiny workers/scripts/processes in the big datacentres - I have a minuscule worker in CF that needs to send one notification once every few days, and I *ALWAYS* get a 429. Always.

So this is good maybe if you're using it to sent from your laptop to your phone.

Re: Ntfy – open-source Push to Mobile

#29

Post by subscribed »

Vaslo wrote: post #15
dewey wrote: post #14

Not Open Source but I’ve been using https://pushover.net/ for this use case since forever. The website still looks the same as on the day I signed up for it probably more than 10 years ago. Never had an issue and using that in all my scripts or cron jobs.

I had all sorts of nfty notification to ios issues despite lots of trial and error and a bunch of AI tokens. I also moved to pushover.

I can't use it at all except for inconsequential notifications from my laptop (residential IP) or my phone (mobile IP).

Re: Ntfy – open-source Push to Mobile

#30

Post by kayson »

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.

Who cares? Battery consumption of Gotify is negligible (it uses websockets). Same with CPU/RAM. What's the benefit of giving Google your notifications?
Post reply on HN