Live data from Hacker News

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

ntfy.sh

121–130 of 306 posts

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

#122
post #106

Earlier quoted context omitted.

I'm not sure if it's worth going any lower than $24/month

If I were to run my own personal instance of this that cost would be quite high. A free Oracle Cloud VM or $5 Digital Ocean droplet would be the way I go.

A free Oracle Cloud VM still costs you your soul, in perpetuity.

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

#123
post #101
post #93

Earlier quoted context omitted.

Well, thinking logically: if everyone really got what they wanted, that question wouldn't be in the FAQ, would it?

Especially with things like notifications, even e2e encryption can't generally provide complete privacy because metadata is data too ;)

Signal does it just fine.

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

#125

Earlier quoted context omitted.

You can probably cut down server cost by half. Have you tried with lower resources or have figured out a minimum requirement for the server? As an experiment I suggest - https://tinykvm.com/ - with FreeBSD or OpenBSD (Linux doesn't really do well with small amount of RAM).

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

Much appreciated my friend. I honestly didn't opt for the cheapest server because I wanted it to run well. I don't want to constantly fight for resources or worry about it. It was supposed to be fast and be able to handle traffic well.

And it is. It's not falling apart from the HN traffic and it has a lot of head room. Plus. It's doing 400k messages a day already easily.

Anyway. Thank you so much for your generosity. I am humbled and thankful for your support.

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

#126

Earlier quoted context omitted.

This is incorrect (at least in my experience). Firebase/FCM is significantly slower in delivering messages than the non-Firebase version (WebSockets or JSON stream, longstanding connection). It was actually mindboggling to me how slow Firebase is in delivering messages (especially when the phone is in doze mode).

But what kind of battery impact do you get leaving a long-running connection open?

Depends on your usage. For me it's around 1% for the entire day: https://ntfy.sh/docs/faq/#how-much-battery-does-the-android-...

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

#127
post #114

Earlier quoted context omitted.

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.

Doesn't work with simplex channels.

It can work with simplex channels if you have the public key of the receiver. Both parties just need to know each other's public keys to create encrypted communication. After exchanging the public keys, it can be one-way communication.

I guess it wouldn't work for a one-to-many channel though, just individual one-to-one channels.

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

#128
post #105
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.

The pitch is that you can go `curl -d "My message" ntfy.sh/my_topic` and it just works. That's impossible if you want E2EE. Fortunately, it's open-source, so if you really want, you can fork the app to add a decryption layer and then use `curl -d "$(echo "My Message" | openssl enc -aes-256-cbc -pbkdf2 -e -k "My Password")" ntfy.sh/my_topic` and that'll be E2E encrypted. Or, you know, host your own ntfy server and tru…

You have perfectly captured my intention. :-) ntfy is supposed to be simple simple simple.

E2E stands in the way in many ways. I have implemented crypto formats and such in the past, and the lack of a standard in this space is really blocking wide spread adoption and interoperability IMHO. That said, I have proposed a design here (https://github.com/binwiederhier/ntfy/issues/69#issuecomment...) that I have already partially implemented, and that seems easy enough to implement in many languages. But it definitely won't be the one-liner anymore.

Post reply on HN