Ntfy – open-source Push to Mobile(ntfy.sh) |
Ntfy – open-source Push to Mobile(ntfy.sh) |
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.
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.
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 as a notification distributor. In addition, I use Proton Mail which doesn't really allow custom notification services. Prism has a custom integration to work around that so your proton mail notifications don't have to touch google services.
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.
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.
I use Pushover for email push notifications- it doesn’t have a subscription and using the proper APIs.