I have no doubt this is a direct result of the feedback in the hacker news thread. Googlers read our comments and take them seriously when there is true merit. Keep making noise folks, it matters.
Product Updates Based on Your Feedback
11–20 of 475 posts
Re: Product Updates Based on Your Feedback
#12I hope this is a wake up call that privacy implications need to be seriously considered during product design (even if the intent was better UX), and hidden changes without any UI/notice is going to make issues blow up far more than if there was clear in-app communication.
Re: Product Updates Based on Your Feedback
#13It seems unnecessary however to auto-log in a person to the chrome browser when there is no such login in the first place to solve this though. It would make more sense to just display a warning when the state is inconsistent rather than start auto-logging people in (regardless of sync state).
Re: Product Updates Based on Your Feedback
#14I have no doubt this is a direct result of the feedback in the hacker news thread. Googlers read our comments and take them seriously when there is true merit. Keep making noise folks, it matters.
The noise was a distraction; the noisy were complaining about sync, which the change did not enable without an additional consent, as always.
Many people _purposefully_ don't want to sign into Chrome. The change suddenly signed them in, without notice or confirmation. That's problematic.
Re: Product Updates Based on Your Feedback
#15I have no doubt this is a direct result of the feedback in the hacker news thread. Googlers read our comments and take them seriously when there is true merit. Keep making noise folks, it matters.
The noise was a distraction; the noisy were complaining about sync, which the change did not enable without an additional consent, as always.
Nice to at least see they're making it opt-out, but the damage has already been done.
Re: Product Updates Based on Your Feedback
#16I have already switched to Firefox and loving it (Facebook container, tracking protection enabled), but these changes are welcome and responsive. I hope this is a wake up call that privacy implications need to be seriously considered during product design (even if the intent was better UX), and hidden changes without any UI/notice is going to make issues blow up far more than if there was clear in-app communication.
To be honest, it’s best to use an independent company for your internet browser. Google’s incentives and business model no longer matches web browsing for someone who cares about privacy.
Re: Product Updates Based on Your Feedback
#17Re: Product Updates Based on Your Feedback
#18Like Eric Law[1], I felt like while there were some rough spots in the UX for the Chrome login and sync features, the issue was very overblown (I'd feel very differently if sync had been enabled automatically). I don't have much more to say than Law does --- except maybe that when your arch-competitor is speaking out on your behalf , maybe the narrative has gone a little haywire. I figured Google would do something c…
One nasty change was that clearing all cookies no longer cleared Google cookies with these changes. That is a big, privacy-impacting change.
With G Cookies also deleted, I may wonder "Why is my picture in the top right but no Google services are using it??". To us, it's clear that chrome sign-in is different from google sign-in, but to others, it may not be.
Re: Product Updates Based on Your Feedback
#19I have no doubt this is a direct result of the feedback in the hacker news thread. Googlers read our comments and take them seriously when there is true merit. Keep making noise folks, it matters.
Re: Product Updates Based on Your Feedback
#20I have no doubt this is a direct result of the feedback in the hacker news thread. Googlers read our comments and take them seriously when there is true merit. Keep making noise folks, it matters.
I wouldn't use those words. I would replace that with "when the backlash is large enough"
Also I read several comments in that thread about how all of that feedback was pointless because the "vast majority of users don't care."
This type of comments always come up after anything a bad company does. You don't need the majority of users to force a change. In fact no movement ever starts with a majority.
That said, Google can no longer be trusted not to screw over Chrome users in the future. Trying to track users this aggressively and then only backing down after a large backlash doesn't really tell me that Google will be playing nice from now on.