Joe, web notifications are controlled at the browser vendor level so ts not part of the open web IMHO. I'm unsure about the rest of the PWA feature set. It likely comes down to implementation but my assumption would be that there are many mechanisms for censorship & surveillance.
-
-
Replying to @sintaxi @joemccann
That's a bit orthogonal. Notifications are possible w/o Push, and browser choice is A Thing (outside iOS, at least).
1 reply 0 retweets 0 likes -
Replying to @slightlylate @joemccann
I can see why you say that given the design choices that were made. I understand the landscape at the time and the goal was to match what native offers. With that said, would you say I'm providing inaccurate or unnecessary information with respect to the question?
1 reply 0 retweets 0 likes -
Alex, shoot me any relevant information you might have on this if you think I got the wrong idea. Also, I'm not entirely sure what you mean by notifs w/o push, if you can clarify on that I'd appreciate it.
1 reply 0 retweets 0 likes -
Replying to @sintaxi @joemccann
Sorry, wasn't meaning to be argumentative! Was only noting that the push backend can be whatever service the browser chooses, so browser choice allows for different implementations.
2 replies 0 retweets 0 likes -
Regarding notifications without push, if you have a document open, the `new Notification(...)` API still works: https://developer.mozilla.org/en-US/docs/Web/API/notification …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @joemccann
Thank you! So if I understand this correctly one could poll for messages in the worker thread and notify the user without the need for a push provider? If so that is really fantastic and addresses my concerns.
1 reply 0 retweets 0 likes -
To further my concerns a big factor for me with web notifs is the developer experience. Seems less than ideal that developers have to register projects with all the browser their users might be using. Its also an additional disadvantage to new browsers that lack marketshare.
1 reply 0 retweets 0 likes -
As I understand this, and I really may not, the way it's _meant_ to work is, the page says "do you want push notifications?", user says yes, browser API returns a push URL and token, page sends that to server, server hits the page URL with the token to send a notification, done.
2 replies 0 retweets 0 likes -
I'm guessing each browser has a consolidated socket that routes the push notifications for all the domains the user has accepted push notifications for - which is why the projects need to be registered by the publishers with each browser vendor. 1 socket = better battery life.
2 replies 0 retweets 1 like
Yep
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.