Chrome Is a Google Service that Happens to Include a Browser Engine
September 24th, 2018In other news, Google tells Congress how write data privacy laws. haha
Via: Bálint’s Extended Musings:
Starting with Chrome 69, logging into a Google Site is tied to logging into Chrome.
This is typically the topic where things are complex enough that tweets or 500 character Mastodon toots don’t do it justice. I’d also mention that I prefer to avoid directly linking people’s posts on this, because I dislike the practice of taking discussions out of their original audience and treating them as official or semi-official communications from a given company.
So what changed with Chrome 69? From that version, any time someone using Chrome logs into a Google service or site, they are also logged into Chrome-as-a-browser with that user account. Any time someone logs out of a Google service, they are also logged out of the browser. Before Chrome 69, Chrome users could decline to be logged into Chrome entirely, skipping the use of Sync and other features that require a login and they could use Chrome in a logged-out state while still making use of GMail for example.
Just to spell it out: this means Google logins for Chrome are now de-facto mandatory if you ever login to a Google site. (Clarification: Sync/browser history/password sharing still requires user confirmation to happen, this is purely about the login itself.)
