Live data from Hacker News

Ntfy.sh – Send push notifications to your phone via PUT/POST

ntfy.sh

181–190 of 306 posts

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#181

Earlier quoted context omitted.

Just gave the developer $50 so he doesn't need to reduce monthly costs. I like the service running well.

That is nice of you and you've helped them to cover server costs for the next two months. Server optimisations can help them reduce the cost further.

I appreciate the dogged pursuit of efficiency, but spending a lot of time optimizing for the current scale and getting costs from $24 per month to $10 per month (or whatever) is likely wasted time if this grows significantly. You have to be able to recognize there’s a lower bound where your costs are low enough it doesn’t matter and even saving 75% isn’t worth thr effort. The author has obviously drawn that line somewhere above $24 per month and that’s perfectly reasonable.

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#182
post #175
post #47

I 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…

Neat. I guess you had to visit pushurl.43z.one once with each browser you want to be notified right? I'm just curious.

Yes, exactly. The pushurl has to be generated with the browser on the device which you want send notifications to. The pushurl is bound to that browser.

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#183

Hey cool, this is my project. Happy to answer questions. Edit: I am also looking for a new opportunity. If you need a good Staff/Principal Engineer, check out my resume here: https://heckel.io/resume.pdf

Look for an email from achilles@relay.cc :) I'm building https://github.com/relaycc/receiver, and we're hiring.

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#184

Hey cool, this is my project. Happy to answer questions. Edit: I am also looking for a new opportunity. If you need a good Staff/Principal Engineer, check out my resume here: https://heckel.io/resume.pdf

What does your reliability look like? Obviously no SLA but what can we really expect? Pay tier available for HA?

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#185
post #44

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…

[deleted]

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#189
post #64
post #61

Earlier 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.

Not on phones.

You have 0 guarantee that the open source code is actually the code that runs on your device. And you have 0 guarantee that the device itself is not compromised. And you have 0 guarantee that the OS is not storing your data.

E2E on mobile devices is a security blanket with holes the size of the solar system.

Re: Ntfy.sh – Send push notifications to your phone via PUT/POST

#190
post #131

Earlier quoted context omitted.

Could the app not take a copy of the per-user private key when it's generated? (I know nothing about mobile security models).

Or when you paste in a key to the app to use for decrypt. Not specific to mobile. Give an app data and it can do what it wants.

I thought maybe mobile OSes might have a decryption sandbox, so apps could manipulate keys without having full access to them.
Post reply on HN