-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
yeah, I know it's shipping. I'm looking for a way to only allow the client to listen for pushed resources from the same origin.
-
...which this API accomplishes.
- 2 more replies
New conversation -
-
-
Or we just kill push for the horrible thing it is
-
Naw; what's horrible is all this custom crap we have to carry around for WebSockets.
- 17 more replies
New conversation -
-
-
I also am concerned about layering this onto SSE semantics; potential mismatches are already being noticed. Deserves to be 1st class.
-
/me sighs I really hate adding more surface area than strictly necessary if we can avoid it.
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
I'll add a 'use-cases' section, but think "why do we need separate infrastructure just for WebSockets?"
End of conversation
-
-
-
Still wrapping my head around it but is it complicated by the fact that h2 connections are shared across tabs/windows and not tied to a doc?
-
To some extent, exposing pushed resources to service workers makes more sense than documents since the shared model is similar.
- 1 more reply
New conversation -
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.