The most telling bit of buried obfuscation is
These changes are all backwards-compatible with other browsers. Thanks, Chrome, welcome to 2013; good of you to get within the past decade of other browsers' privacy behaviours.
Note: yes, SameSite is circa 2016 (
RFC6265 [tools.ietf.org]) but much of that behaviour was introduced in Safari circa 2013.
SameSite overall is far less damaging to Google, due to it's ubiquitous reach, than it's 'third party' ad network competitors.
Plus, if one is logged into Google all this cookie SameSite privacy 'nonsense' is moot.
Note: Google is THE maestro of tracking prevention work arounds; always a joy to parse their announcements.
Note: how sites manage SameSite looks, to some extent (will have to wait and test), to mitigate it's tracking 'damage' potential. It will be interesting to watch who 'get' this and who do not.
Note: there remain other quite viable xSite tracking mechanisms than cookies. They are becoming (slightly) more prevalent due to EU's 'cookie' et al regulations and competitors' increase (which will be heightened by this announcement) in browser cookie blocking/containment. Will be interesting to see which are most commonly used/abused and various browser/regulatory reactions.
Note: eg: ye olde 'link decoration' aka using query strings to (among other info passing possibilities) set first party cookies AND can track cross 'companion' sites.
Note: used as example due to WebKit aka Safari announcement last month on
changes in ITP 2.2 [webkit.org] addressing link decoration.
Note: never out a competitive advantage before it's gone public.
Final thought: in same post Google also mentioned making fingerprinting more difficult (minus actionable info), which will be intriguing to follow... as currently:
* 99.9% accurate identifying same device same browser over 90 days.
* 97.2% accurate identifying same device xBrowser over 90 days.
* 90.5% accurate identifying xDevice xBrowser over 90 days.
And nary a cookie.