Another good open-source self-hosted alternative is Gotify.
Ntfy.sh – Send push notifications to your phone via PUT/POST
71–80 of 306 posts
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#72Earlier quoted context omitted.
If you don't trust the person that wrote the software, it doesn't matter if it's E2E encrypted or not. There could be a back-door
E2E encryption happens on the client side, not on the server side. Therefore, no need to trust anybody, as long as the software is open-source.
If you run binaries compiled by the author of the software it wouldn't matter that it is open source, so play store is out of the question. So then it must be open source and you must use distributor you trust: your distro maintainers and F-Droid.
Also you must trust that people did really take a look at the code.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#73Earlier quoted context omitted.
Why couldn't the entire system be E2E encrypted by default, though? In 2022, that's my standard expectation from any service. Even such things as Pocket / Instapaper / Raindrop should come with E2E encryption by default. It's better for the service provider, too: no issues with GDPR, or in case of a database hack.
If you don't trust the person that wrote the software, it doesn't matter if it's E2E encrypted or not. There could be a back-door
If you don’t trust a communication channel, you could always do a Diffie-Hellman key exchange in the clients which lets you create a shared encrypted channel between two parties by sharing public keys. This works even if they are trying to monitor you.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#74From the FAQ[1]: > Will you know what topics exist, can you spy on me? > If you don't trust me or your messages are sensitive, run your own server. This is the way. No pinky promises in whitepaper format[2] that leave out the most important bits, no meticulously constructed but entirely meaningless marketing statements[3][4], but unassuming and deferential logic with a mitigation path. 1: https://ntfy.sh/docs/faq/#wi…
I wish they also provided the code to run own server of ntfy, but instead it looks like they meant "write and run your own server".
Didn't look deep but looks like the sever code is provided + multiple ways of self hosting.
https://github.com/binwiederhier/ntfy/blob/main/server/serve...
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#75From the FAQ[1]: > Will you know what topics exist, can you spy on me? > If you don't trust me or your messages are sensitive, run your own server. This is the way. No pinky promises in whitepaper format[2] that leave out the most important bits, no meticulously constructed but entirely meaningless marketing statements[3][4], but unassuming and deferential logic with a mitigation path. 1: https://ntfy.sh/docs/faq/#wi…
Why couldn't the entire system be E2E encrypted by default, though? In 2022, that's my standard expectation from any service. Even such things as Pocket / Instapaper / Raindrop should come with E2E encryption by default. It's better for the service provider, too: no issues with GDPR, or in case of a database hack.
The most important bits aren't the technical aspects, but rather who controls them.
It is entirely meaningless when the keys are generated by a closed source application, when there exists no way to verify that the data isn't exfiltrated before its encryption or after its decryption, or when the only transportation method is entirely in an untrusted party's hands.
When all those things are controlled by the same entity, especially one with a history of abusive and manipulative behaviour such as the operator of WhatsApp, it's not "encryption" but a "bad joke".
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#76From the FAQ[1]: > Will you know what topics exist, can you spy on me? > If you don't trust me or your messages are sensitive, run your own server. This is the way. No pinky promises in whitepaper format[2] that leave out the most important bits, no meticulously constructed but entirely meaningless marketing statements[3][4], but unassuming and deferential logic with a mitigation path. 1: https://ntfy.sh/docs/faq/#wi…
Why couldn't the entire system be E2E encrypted by default, though? In 2022, that's my standard expectation from any service. Even such things as Pocket / Instapaper / Raindrop should come with E2E encryption by default. It's better for the service provider, too: no issues with GDPR, or in case of a database hack.
Encryption by default eliminates the biggest advantage: simplicity. But as an option, it's an useful addition that will be implemented sooner or later.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#77When I was making my IoT washing machine sensor, I used Blynk.io to push notifications to my phone but of course that service became commercialised and is no longer free. I could not find any nice easy to use alternative except for Telegram which is what I use now. This service looks exactly like what I would need and I appreciate the promise to keep it open source.
https://pushover.net/ Has existed for several years. It works great for me.
I'm using Pushover a lot, it exists for a very long time, never changes and just works. It's also very easy to wire it up to existing tools as it can listen to webhooks.
In my case I just did that recently to receive webhooks and send them to my phone: https://blog.notmyhostna.me/posts/push-notifications-from-ap...
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#78Keep in mind that ntfy works with a bunch of backends. You can send the notifications to Telegram, jabber/XMPP, IRC (using my own https://n.tkte.ch ), Slack, etc, etc. So, you probably don't have to actually install anything new to receive notifications and can just use what you've already got.
I don't think ntfy.sh does that, but are you talking about https://github.com/dschep/ntfy ?
You are 100% correct. Boy that's confusing. I thought they'd just gotten a new site!
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#79From the build instructions: > You should download Android Studio (or IntelliJ IDEA with the relevant Android plugins). Everything else will just be a pain for you. Do yourself a favor. I'm not into mobile programming, and I wonder what is behind this statement.
Native mobile apps are typically built using Android Studio and its tooling. On the iOS side, it's Xcode and it's tooling
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#80Could this potentially replace Firebase Cloud Messaging for push notifications?