> The main thrust though, is that this doesn't actually solve anything for end users that the Google Chrome team says it does.
Yes it does, it solves the exact problem described right in the article. Before this change, there would be a seperate log-in process for Chrome versus every other google service (which normally all share your current login status). Now, your login status is shared between every google service including Chrome, as a layperson would expect. Previously people who wanted to be logged into Chrome AND other google services would have to complete the login process twice which could be confusing for novice users.
We could apply the principle of least astonishment to get a feel for correct behaviour without resorting to sterile arguments about what proportion of users understand the difference between a web site and a web browser.
If they looked at a slightly risque URL on their phone, would the average user expect Chrome on their laptop to autocomplete that URL?
The current behavior does not activate syncing by default in spite of the slippery slope arguments being made here. Furthermore i think most users would in fact expect syncing like that to work with minimal configuration in this day and age.
Please be civil with people who have a different perspective. The implication that the opposing position is outmoded is not a logical argument, it's an insulting one. "In this day and age," I'd think we could learn to be less dismissive of people.
Well he was replying to me and I didn't read him as uncivil at all.
His response ("syncing is expected") is completely on-point when talking about the PoLS. I disagree, obviously, and think syncing is scary voodoo magic. I don't see how you can say "users are unsophisticated and don't understand the difference between web sites and web browsers" and also say "users are sophisticated and expected config syncing".
Unfortunately, to get any further we have to test users.
If I’m not mistaken, this also ensures that when you sign out of Gmail, you are signed out of Chrome (no?). That seems like a win for user privacy, insofar as it addresses the likely failure mode of mistakenly leaving the browser signed in after signing out of the website.
No. Pauses sync but doesn't sign out Chrome. So a person could still see your history/bookmarks/passwords in the logged-in browser. They just can't wipe your cloud data (which I think was the same before this update).
Yes I was thinking about chrome profiles. My mistake. But from what I remember, when you choose to log out, Chrome prompts you if you want to wipe your local data. So logging out locally allows you to protect some data. I think there was a way to log out remotely (tricky/weird way), though again without the local-wipe prompt.
I also just tried signing in to chrome (69.0.3497.100), and it tried to sync immediately again, so I'm not sure where the "sync is optional" idea comes from?
> there would be a seperate log-in process for Chrome versus every other google service (which normally all share your current login status).
Sorry, not much of a Chrome user here. Why would I want to “sign in” to a web browser? I’ve been browsing the web successfully for decades without doing so. I don’t sign in to my text editor either.
I understand the privacy concerns, but I find it very useful as I go between desktop and laptop often. It syncs bookmarks, history, tabs, settings, autofill, extensions, etc.. There have been plugins for this stuff for decades as well, so it is something that people find useful.
Yes it does, it solves the exact problem described right in the article. Before this change, there would be a seperate log-in process for Chrome versus every other google service (which normally all share your current login status). Now, your login status is shared between every google service including Chrome, as a layperson would expect. Previously people who wanted to be logged into Chrome AND other google services would have to complete the login process twice which could be confusing for novice users.