One way to think about the declarative vs. imperative debate that arises here (and in nearly every other web API) is a tension between "who do you trust?" (at a baseline level) and "who do you appeal to when that goes wrong?" Base-case trust usually predicts systemic outcomes.https://twitter.com/slightlylate/status/1134337290979794945 …
-
-
Hitchen's razor is a tough (but fair) master.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
protecting users in the case of NPAPI is kind of an a/b thing. the people who created lots of content (many of them to pay rent) that depended on NPAPI were screwed because no real html5 alternative to NPAPI unity (or flash) existed and even now they barely exist
-
there's always a good reason to do it, but we've had large swathes of important web history + content broken for security reasons 3+ times now. i suppose compared to that, most existing ad blockers breaking is not a big deal
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.