Chrome used to be neutral with respect to Google sites. Now that Google sites can make changes to browser state that other sites can't, and set cookies that are exempt from clearing, the neutrality is gone. With Chrome's/Google's majority market shares, this is worthy of concern.
-
-
There are examples in the replies of Chrome not always being so neutral, although they have since corrected them. Hopefully they will do the same with the new auto-login feature, though it's unclear what that would look like, given how Google-specific it is.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Only one of these is true.
-
The pinning code has not yet been removed (because of unittest issues, sigh), and only targeted dynamic pins. Static pins, including Google, remained. QUIC was whitelisted for only Google origins several times (although sometimes for security reasons). google-QUIC != IETF-QUIC.
-
Is there still an intent to remove static pins in the future?
-
Yes, at some point, that is the goal. The blink-dev@ intent thread captured some of the trade-offs there and challenges with nailing down concrete dates and dependencies.
End of conversation
New conversation -
-
-
They’ve done this in the past too. NaCl was whitelisted in the browser to http://google.com URLs for a while.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.