Live data from Hacker News

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

ntfy.sh

221–230 of 306 posts

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

#221

Earlier quoted context omitted.

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

Your approach is great. It’s odd to see so many penny pinching comments here, the HN crowd usually skews the other way.

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

#223
post #218

Earlier quoted context omitted.

> My point is very clear and simple: all private communication on the internet should be E2E encrypted by default, unless there is a good reason not to. Are you counting HTTPS as “E2E encrypted”? Because if not, consider that we do private communication over mere HTTPS all day long. Me loading the HN web page and having my own personal rendering of it with my user cookie header and all my upvote/downvote/karma/profil…

> Are you counting HTTPS as “E2E encrypted”? No. > Because if not, consider that we do private communication over mere HTTPS all day long. Me loading the HN web page and having my own personal rendering of it with my user cookie header and all my upvote/downvote/karma/profile state is private communication, for example. Because there is a good reason for it: it wouldn't work well with E2E encryption.

Well, ok, I guess we can use that as a justification for anything then. For example, the “good reason not to” use E2E for ntfy could be “market analysis says the small and somewhat theoretical benefit isn’t worth the complexity.”

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

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

Is the code public? Seems simple to implement. But I'd rather copy and paste.

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

#225

Earlier quoted context omitted.

https://ntfy.sh/docs/faq/#what-are-the-uptime-guarantees I guarantee for nothing, since this is a spare time project. That said, I have had zero outages in 11 months, see https://ntfy.statuspage.io/ When it outgrows the single EC2 instance, I'll likely start building some distributed thingy to spread the load and do some HA things (sounds like fun). Probably just a load balancer and 2-3 instances with a rqlite backen…

rqlite[1] author here, happy to answer any questions about it if it helps. rqlite will give you HA, but won't help with load (rqlite replicates for reliability, not for write performance). But I like to think the it'll give you solid -- and simple to use -- HA. Replicated just replaced their use of Postgres with rqlite for this reason[2]. [1] https://github.com/rqlite/rqlite [2] https://www.replicated.com/blog/app-ma…

I love the internet. Random people meet in so many places. rqlite is awesome. Fantastic project.

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

#226

Earlier quoted context omitted.

Here are some stats from last night showing the volume of messages: IPs: 9756 Clients: 9980 - Google Play: 2796 - F-Droid: 5985 - iOS: 794 - curl: 62 - other: 343 Messages: - Successful: 310076 - Failed (rate limited): 104741 - Failed (other): 6511 Top publishers (* = limit exemption): 22908 matrix.org* 22352 matrix.gateway.unifiedpush.org* 18286 up.schildi.chat* 16134 192.124.x.x 14056 matrix.envs.net* 13376 108.35.…

Watch out for data transfer costs on aws after HN

Thanks. I'll keep an eye on it. I have a lot of rate limiting in place, but for static resources it could probably be tighter.

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

#227
post #218

Earlier quoted context omitted.

> Are you counting HTTPS as “E2E encrypted”? No. > Because if not, consider that we do private communication over mere HTTPS all day long. Me loading the HN web page and having my own personal rendering of it with my user cookie header and all my upvote/downvote/karma/profile state is private communication, for example. Because there is a good reason for it: it wouldn't work well with E2E encryption.

Well, ok, I guess we can use that as a justification for anything then. For example, the “good reason not to” use E2E for ntfy could be “market analysis says the small and somewhat theoretical benefit isn’t worth the complexity.”

Private messaging is one of the primary use cases for E2E encryption in the entire tech industry.

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

#228
post #192
post #161

Earlier quoted context omitted.

That would be great! I've only had a quick look at the docs, but the API seems reasonable: https://docs.joinmastodon.org/methods/apps/oauth/ https://docs.joinmastodon.org/methods/statuses/

It's not the sending the messages that has me stumped, it's the setup of the server (the hosting of it itself). Do you know of a public service that exists i could build/test the Apprise plugin against? Would love just even temporary access to a server to perfect its design (then my account could be terminated)

You don't need to host a Mastodon instance yourself. Plenty of them are open for registration :)

e.g https://masto.ai/ or https://fosstodon.org

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

#229
post #101

Earlier quoted context omitted.

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

You solve that by forwarding/decrypting/adding noise between servers, enough to cover metadata traffic you generate. The only data you reveal is anyone listening know you might have used it at some point. See https://vuvuzela.io/ I suspect it is named so because it uses a lot of bandwidth.

It's of course possible to mitigate, but that's somewhat more involved than "just" sprinkling e2e encryption on top ;)

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

#230
I'm not a hater, I am genuinely curious, how does something like this get to 800 votes on HN and 4.4K stars on GitHub?

I mean, it's just... a pub/sub server... using HTTP? With a thin UI for web/mobile? I'm obviously missing something, so what is it?

Again, not a hater, even though it may come off like I am, I'm just honestly wondering what makes this special. From first glance it seems like something most devs can hack in an hour or two.

Post reply on HN