I have a dumb thought, allow me to burden you with it! So the issue is "publicness", right? How do we know this fetch won't hit an internal system. How about we force public DNS lookup + TLS? We have a DOH resolver, why not use it here?
-
-
You eventually see patterns to arguments: 1.) Ugh, do we have to? 2.) Fine, but <thing wrong with sketch> 3.) But if you lead, others won't have already implemented; where is your beloved interop *then*!?!!! 4.) Ok, it's *nearly* everywhere, but IE6 5.) Now that we have this...
-
Anyway, that's all by way of saying Twitter is the worst for this. Sorry for the noise!
End of conversation
New conversation -
-
-
for normal features, you can fall back when the feature isn't supported. but here, the goal is to remove server-side functionality, which you can't do until all clients support it. so AFAICS the barrier to success is way higher than for normal features
-
Nah, this is identical. You'll be able to measure the incremental difference in a service's monthly bandwidth costs, which will scale down linearly with client adoption. No large stair-step! As good as this sort of thing gets, TBH
End of conversation
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.
