From 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…
Is that really much different than anything else other than an faq? No promises so they could be selling your info more than anyone else…
Ntfy.sh – Send push notifications to your phone via PUT/POST
171–180 of 306 posts
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#172Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#173Earlier quoted context omitted.
https://pushover.net/ Has existed for several years. It works great for me.
Additionally they support "Critical Alerts" on iOS for when you really need to get a notification regardless of whether or not you've muted your device. Probably something similar is possible on Android as well?
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#174Earlier 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.
Genuine question - have you ever implemented an E2E encrypted system? Because it's not particularly easy to do, and there are a lot of caveats and drawbacks. Let me rephrase your assumption: "Why couldn't you just mail me the letter in a 100lb safe. In 2022, that's my standard expectation from any service". So - are you willing to pay to ship 100lbs for every letter you send? Are you meticulously managing the details…
Clients encrypt data in the browser, share id of the data and key (+ optional password). Some other clients receive id of the data and the key and read it.
For a notification service, you would just need a setup step to generate a key and store it in the browser + on the phone. That said, I'm not sure I understand why would someone need to notify its own phone.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#175I sometimes use my little service https://pushurl.43z.one/ If I need to notify my desktop browser or phone with a notification triggered by some code. I just go to the website with my browser click generate. Then in my script I do `curl $pushurl?title=jobdone`. When it gets triggered a notification popups on my phone that says "jobdone". It uses the native browser web push API so I don't need to install anything extr…
I'm just curious.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#176When 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.
Personally I setup a Slack server and use webhooks to push events to a channel there. Works great :)
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#177Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#178Earlier quoted context omitted.
You plucked the word "promises" out of the context it was written in.
I don’t understand what you mean.
Difference here, is that the promises are verifiable and their concequences avoidable altogether (by self compiling and hosting). The developer also acknowledges the existing holes rather than misdirecting away from them.
Edited my previous comment slightly as it was not at all my intention to accuse you of malicious intent. My apologies if it might have have come across that way.