Hacker News Reader

Comment by EngineeringStuf | Hacker News Reader

I'm surprised to learn that this isn't an open standard. E.g I must make an API call to a browser vendor. Is this a form of vendor lock-in?

View on HN

It’s an open standard but it’s centralized, and not all of it is covered by an open standard.

Here’s the page about browser support. https://github.com/web-push-libs/web-push/tree/master#browse...

Well, in the git repo, they directly link the RFC https://datatracker.ietf.org/doc/html/rfc8030

Wouldn't this be easier to maintain a websocket/socket.io type of connection with the web page? And just push new events from the server to the page directly?

That wouldn’t scale, and wouldn’t work if the page wasn’t open and active (e.g. suspended tabs, closed browser, etc)

It would open up a powerful new avenue for tracking users if every browser maintained a permanent, identifiable TCP connection, even when the page was closed, and kept it up as the user moves between wifi and mobile data.

That would waste battery and other resources having to keep a connection open to every possible site that could possibly send you a notification.

Is there a meaningful difference between waking up the CPU from sleep to maintain a single tcp connection vs waking it up to maintain 50? Provided of course all 50 require a keepalive packet at the same time, I don't think so. But feel free to correct me.

Yes, because the single connection to the push server is hard optimized to stay alive regardless of NAT etc. Cellular carriers have special handling for APNS and GCM, for example. (And I assume there's some kernel & firmware hacks in devices to further offload some handling of APNS/GCM protocol)

> Cellular carriers have special handling for APNS and GCM, for example

Would you have any extra info on this? Thanks!

Not off the top of my head, but I remember the iPhone in its early years required specific carrier support because of that permanent APNS connection. Can't find a source for this now but I remember that being one of the reasons that iPhone 2G/3G/3GS wouldn't work (well) on other carriers even after SIM unlocking.

I assume nowadays it's more to do with GCNAT pruning connections to APNS/GCM less heavily than other "regular" connections (which is doable given that APNS has specific ports[1]), or cell carriers having different routing & handling for push notifications IPs, but that's just speculation.

1: https://support.apple.com/en-us/102266

Reply on news.ycombinator.com