I'm the maintainer of ntfy. Happy to answer questions. Sorry that I'm late to the party :-)
Thank you for ntfy. I self host it and love it.
Ntfy – open-source Push to Mobile
41–50 of 53 posts
Re: Ntfy – open-source Push to Mobile
#42I wrote a mini bridge for Linux desktop notifications (via notify-send) for anyone that's interested:
Re: Ntfy – open-source Push to Mobile
#43I used it for a while. The iOS client had issue showing images (I can’t remember the details, it’s probably fixed by now) and the PWA wasn’t too reliable. I had to frequently login again to get it back in a working state
I ended up switching to pushover and had no issue since
Re: Ntfy – open-source Push to Mobile
#44I 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.
If you use ntfy.sh and don't use instant delivery, ntfy uses Google's FCM for delivery, which is what everyone else does. It doesn't require a foreground service and has no battery impact.
ntfy offers you additional options with instant delivery or the selfhostable server. That requires a server connection and does impact battery a little. On my phone it doesn't show up in the list it's so low, but others have reported more consumption
Re: Ntfy – open-source Push to Mobile
#45Earlier quoted context omitted.
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.
Aren’t the requests https?
Or you mean you are trying to hide from a network where you are mitm attacked?
Re: Ntfy – open-source Push to Mobile
#46Silly question maybe: why use this at all when you already have a well known, decentralised, vendor-independent, almost real-time, and persistent notification system at your disposal? I'm talking about email of course.
Re: Ntfy – open-source Push to Mobile
#47Silly question maybe: why use this at all when you already have a well known, decentralised, vendor-independent, almost real-time, and persistent notification system at your disposal? I'm talking about email of course.
Email notifications are dependent on whatever push notifications your email app are using. Either it's set to reach out and check for new messages at a set interval or use a service like bluemail where you hand over your credentials and they send you a proper push via APNS or Google. Either way not as reliable in my experience.
Re: Ntfy – open-source Push to Mobile
#48I'm the maintainer of ntfy. Happy to answer questions. Sorry that I'm late to the party :-)
The problem with ntfy for me is that I get notifications on my mobile through the ntfy app. On desktop, in the browser (Safari on Mac), I only get notification pop-ups when the website is open.
The worst part is that I don’t even see the notifications on the website that I received on my mobile while the website wasn’t open.
Re: Ntfy – open-source Push to Mobile
#49I'm the maintainer of ntfy. Happy to answer questions. Sorry that I'm late to the party :-)
The problem with ntfy for me is that I get notifications on my mobile through the ntfy app. On desktop, in the browser (Safari on Mac), I only get notification pop-ups when the website is open. The worst part is that I don’t even see the notifications on the website that I received on my mobile while the website wasn’t open.
Go to ntfy.sh/settings and enable background notifications. Or do it like I do it an pin the tab and just leave it open.
Unless you have a pro account, notifications are only cached on the server for 12h so that's why you may miss old notifications.
Re: Ntfy – open-source Push to Mobile
#50Earlier quoted context omitted.
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.
Aren’t the requests https? Or you mean you are trying to hide from a network where you are mitm attacked?
Yes, they are https so security is not a concern.
I want to crowd blend at the network level so that my requests don't aversive that I'm using a privacy notification system (or a VPN).