Live data from Hacker News

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

ntfy.sh

61–70 of 306 posts

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

#61
post #58
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…

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

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

#62
post #61
post #58

Earlier 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

which software ? You might have 3rd party client implementation that talks with another client and only server would be "unknown" party.

E2E allows both clients to talk to eachother without server having a way to snoop on

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

#63
post #55

Keep 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?

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

#64
post #61
post #58

Earlier 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

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.

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

#65
post #58
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…

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 and convenience usually don't go well together. ntfy was mainly built for simplicity. That said, I have designed and started working on E2E here: https://github.com/binwiederhier/ntfy/issues/69

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

#66

Earlier quoted context omitted.

The Google Play services question is answered here: https://ntfy.sh/docs/faq/#why-is-firebase-used And yes, you need to disable battery optimization if you don't want to use Firebase. On my phone it uses 1% battery in a full day (17h).

Even if you disable battery optimization it's going to depend on your phone if it will actually honor it (and not kill the app). This site: https://dontkillmyapp.com/ shows which phones behave correctly.

And if you change the settings that will make your phone behave nicely it often severely impacts battery life ;/

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

#67
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…

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

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

#68
post #58
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…

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 of how to handle locking and unlocking that safe? Are you working out the details on recovery and storage, handling lost devices, configuring a communication channel for sharing certs/keys, managing several crypto dependencies and libraries - all so that you can go "Hey - what's up!" in a notification to your phone?

Or should you just stop whining - accept that this is free - and take the authors advice and host it yourself?

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

#69
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…

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

The server is open source.

https://github.com/binwiederhier/ntfy

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

#70
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…

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

https://ntfy.sh/docs/faq#can-i-self-host-it

The next topic on the FAQ. Also install instructions are provided.

Post reply on HN