11–20 of 53 posts
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.
Been running ntfy in my homelab for several years. Always works great!
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.
Been running ntfy in my homelab for several years. Always works great!
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.
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 use it to send commands and URLs between my devices.
On Linux you can do `ntfy sub` and on android you can have Tasker react when a ntfy notification arrives based on its title and contents. So on just about all my devices I have a background script running that is subscribed to a "DeviceCommands" channel that checks if the Title of new messages contains the device hostname or not. If it does it triggers a script based on the contents of the body.
E.g.:
Title: Pixel8
Message: https://kagi.com
Will automatically send the URL to my browser.
Or:
Title: LivingRoomPC
Message: Shutdown
Will shut down the computer.
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
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.
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.
Love this service! I use it to send commands and URLs between my devices. On Linux you can do `ntfy sub` and on android you can have Tasker react when a ntfy notification arrives based on its title and contents. So on just about all my devices I have a background script running that is subscribed to a "DeviceCommands" channel that checks if the Title of new messages contains the device hostname or not. If it does it…
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.