News for hackers. Stuff that matters.
Re:Product Updates Based on Your Feedback by tptacek on Tuesday September 25, 2018 @08:42PM (#18071744)
Like 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 cosmetic (again, that's all that I think they really needed to do) to clear up the misconceptions here, but they've added a Matthew Green switch (which is what we all need to call it from now on). That's better than I'd hoped for.

[1]: https://textslashplain.com/2018/09/24/chrome-sync/

Re:Product Updates Based on Your Feedback by statictype on Wednesday September 26, 2018 @12:14AM (#18072728)
The sync thing was overblown. The cookies thing was a bit more concerning to me.

Not so much from a privacy angle but from more of a 'Chrome has lots its way' angle.

A lot of our software's more complex interfaces are Chrome-first since its faster to develop - yesterday was the first time I made a serious consideration to change that approach.

Glad to see they are listening to user feedback and reacting quickly.

Re:Product Updates Based on Your Feedback by kodablah on Wednesday September 26, 2018 @12:24AM (#18072774)
> Glad to see they are listening to user feedback and reacting quickly.

I consider an opt-out as paying lip service to the feedback. Clearly they feel the default is more important than the generated angst. Reaction clearly needs to be even stronger to affect real change. An opt-in (e.g. a dialog on next Google login from Chrome asking for feature enable) is a compromise, an opt-out is to appease the temporarily upset while keeping all that they added in place and defaulted.

This is not an olive branch, don't accept it, condemn the continued incremental marriage of Google browser+services, and continue to move on and de-google yourself where you reasonably can.

Re:Product Updates Based on Your Feedback by derefr on Wednesday September 26, 2018 @03:08AM (#18073442)
You seem to be looking at the choice of opt-in vs. opt-out from the perspective of a user who actually cares about the feature.

Much more common, though, I'd say, is the type of user who will accept whatever the default is, because they just don't care.

Compare: the organ-donor registry. When it's opt-in, most people don't opt in. When it's opt-out, most people don't opt out. Most people just don't care.

If you think something is good for people, you have to consider the large group of users who don't want to put in the time/energy to evaluate whether the thing is good for them, but just want the program to shut up and do what it does by default—whatever that is.

Re:Product Updates Based on Your Feedback by cm2187 on Wednesday September 26, 2018 @03:56AM (#18073730)
It’s not just that the user doesn’t care. I don’t want to have to monitor constantly hackernews to find out what new invasion of privacy google will sneak in discretely, even if there is a switch somewhere to opt out. I want to be able to rely on the tools I use.
Re:Product Updates Based on Your Feedback by joshuamorton on Wednesday September 26, 2018 @11:03AM (#18076648)
The issue with this line of thinking is that this change isn't really a privacy invasion. Account consistency didn't at all affect privacy. You still had to opt in to syncing, which did affect privacy.
Re:Product Updates Based on Your Feedback by cm2187 on Wednesday September 26, 2018 @11:35AM (#18076991)
I would be surprised if it didn't affect google's capacity to track you nominally.

When I flush all cookies from my browser session, and open a new session, I am a new user to google's various tracking mechanism. If I am an authenticated google user, then I am not.

Re:Product Updates Based on Your Feedback by joshuamorton on Wednesday September 26, 2018 @11:52AM (#18077181)
I would agree that there was at least potentially an issue due to it re-logging you in. But I'll note that no one wrote a blog post about that. Someone just mentioned that on twitter after this was already a big "controversy".

In other words, you had half of HN claiming to be leaving Chrome over something they had no reason to believe had any privacy implications, and in reality, has either 0, or really close to 0, actual privacy implications.

I made a claim about HN being a small group in the grand scheme, and someone countered by claiming that most users didn't understand what was changing. But I think the funny thing is that the average user, who had the understanding that "literally nothing" was changing, would have been closer to the truth of the situation than the average HN commenter.

Not to say that the result of the hullabaloo was bad, I actually think this set of updates only improves things over where they are now, but its still a really strange sequence of events.

Re:Product Updates Based on Your Feedback by cm2187 on Wednesday September 26, 2018 @12:23PM (#18077549)
No the problem is tracking. It basically makes google tracking cookies un-deletable. I don't see how this is a non-issue from a privacy point of view.
Re:Product Updates Based on Your Feedback by joshuamorton on Wednesday September 26, 2018 @12:28PM (#18077606)
Well no, logging out in the browser would still delete them.

This is kind of what I mean, you can't talk about this without hyperbole.

Re:Product Updates Based on Your Feedback by cm2187 on Wednesday September 26, 2018 @12:36PM (#18077682)
But if it re-logs you back in when you re-open the browser, it may be technically a different cookie, but it is a cookie with your real identity attached to it (as opposed to an anonymous cookie like if you started a fresh session on an older version of the browser). So practically, that has the same effect that if the cookie was never deleted.
Re:Product Updates Based on Your Feedback by derefr on Wednesday September 26, 2018 @01:24PM (#18078217)
The parent means, logging out and staying logged out of the browser, would have exactly the same behaviour as logging out of your Google Account would in Firefox.

The whole point of the feature was just that:

1. “are you logged into your Google Account from the perspective of Gmail et al” is now the thing the browser chrome itself reports; and

2. you now need to be logged into your Google Account in the cookies sense for Chrome sync to function; logging out of your Google Account turns off Chrome sync.

Before, people could be in a state where they have Chrome sync enabled with foo@gmail, but are not logged into foo@gmail from a cookies perspective, and are potentially even logged into bar@gmail.

This is the state that has been eliminated—now, the browser chrome’s login state reflects your Google Account web-cookie login state, because they’re one-and-the-same; and every method that logs you out of your Google account from a web-cookie perspective, also logs you out of Chrome (and vice-versa.)

Consider the privacy implications of someone who logs out of Gmail, but is still logged into Chrome sync as said Gmail user; and then lets someone else use the computer. That is what is no longer possible.

It’s a privacy improvement targeted at the people who expect “logging out” of their Google account to be one unilateral action that frees a computer of all artifacts related to their original logging-in. Which, until recently, wasn’t true: if you originally logged in by entering your credentials into the “new Chrome profile wizard” (where they set up the credential as both your synnc and web-cookie credential), and then logged out of one, it wouldn’t affect the other.

Re:Product Updates Based on Your Feedback by joshuamorton on Wednesday September 26, 2018 @01:47PM (#18078461)
No, I mean you can log out of your Google account in the browser and it actually logs you out. Deleting your cookies does re-create a cookie (which is weird), but logging out in browser (I see it as "Exit Joshua" on Chrome on OSX) deletes Google cookies and doesn't recreate any.
Re:Product Updates Based on Your Feedback by dredmorbius on Wednesday September 26, 2018 @03:42PM (#18079523)
It is difficult for me to assess the validity of this statement. I cannot tell if the behaviour is or is not a privacy invasion. What I can tell is that it is not in the direction of greater privacy. That it is not a feature I'd requested, want, or am comfortable with. And it's in line with multiple past trust violations.

That Google are announcing walking this back within days of release and publicity suggests some measure of the storms roiling the 'Plex presently.

Re:Product Updates Based on Your Feedback by joshuamorton on Wednesday September 26, 2018 @04:12PM (#18079807)
>What I can tell is that it is not in the direction of greater privacy

For you, it may be a no-op, but for many users, it is a net increase in privacy (people who use multiple accounts or who use accounts on shared computers).

>That Google are announcing walking this back

Erm, sort of, I guess. There are some small changes.

Re:Product Updates Based on Your Feedback by dredmorbius on Thursday September 27, 2018 @02:06AM (#18082385)
...for many users...

What numbers, precisely, do you have on this? Because it sounds to me as if you're arguing from a position of ignorance.

There might be some benefit to the small number of users who 1) have multiple devices and 2) share one or more of those amongst several other people in the same account in ways that this Chrome feature ... might address. But this doesn't strike me as some overwhelmingly large use case.

The system for user separation on shared computers is called ... user accounts. Which every mainstream consumer operating system has supported for the past 17 years (Windows XP being the latecomer to this game.)

Otherwise, this is a broadening of Google's ever-expanding ingestion of user data, either directly or by way of one more (or an incremental series of) "small change". If I notice my enemy maneuvering me to his advantage, I counter that maneuver. In my case, it's meant uninstalling Chrome and Chromium from any systems on which that's possible.

(My much-regretted purchase some years ago of an Android tablet being the primary exception, though I'm resolved to not repeat that mistake, despite a dire lack of viable market options presently. Purism and Ubuntu may be nearing useful products.)

...small changes...

In the Universe in which I inhabit, Google specifically addressed user feedback and sign-in changes. I cannot find your characterisation of their announcement as accurate under any charitable interpretation.

Re:Product Updates Based on Your Feedback by joshuamorton on Thursday September 27, 2018 @02:12AM (#18082406)
I don't have that data on hand, but the chrome team apparently does.

Certainly, for you or I, user accounts (and incognito windows) solve most of the problems that this change fixed. But most users aren't you or I.

Re:Product Updates Based on Your Feedback by dredmorbius on Friday September 28, 2018 @05:23AM (#18092038)
Google's claimed usage data has stood up poorly to my investigations in the past.
Re:Product Updates Based on Your Feedback by grey-area on Wednesday September 26, 2018 @04:31AM (#18073927)
If you think something is good for people

Therein lies the disagreement - Google thinks it is good for people to log in to Google services via their browser, and to always be logged in (it's certainly good for Google!), therefore they choose these defaults, opting in to login and to tracking.

Many disagree.

Re:Product Updates Based on Your Feedback by cm2187 on Wednesday September 26, 2018 @04:45AM (#18074002)
Like Apple thinks it's "good for people" to have a 40% markup on their product...
Re:Product Updates Based on Your Feedback by dredmorbius on Wednesday September 26, 2018 @03:32PM (#18079438)
If you want to participate in a debate or discussion, then ddo so. Whataboutism, deflection, projection, etc., are not that.
Re:Product Updates Based on Your Feedback by babuskov on Wednesday September 26, 2018 @03:25AM (#18073527)
> Compare: the organ-donor registry. When it's opt-in, most people don't opt in. When it's opt-out, most people don't opt out. Most people just don't care.

Most people don't know it exists or that they have an option. You cannot care about something if you don't know it's there.

Re:Product Updates Based on Your Feedback by jee1shi on Wednesday September 26, 2018 @03:45AM (#18073661)
> Most people don't know it exists or that they have an option. You cannot care about something if you don't know it's there.

Most people won't know that these chrome features exist. Most people don't go digging through options and settings, they just download chrome and go, go, go.

Re:Product Updates Based on Your Feedback by babuskov on Friday September 28, 2018 @04:59AM (#18091926)
Exactly. Same as the organ donor thing. They don't KNOW. If they knew they would CARE.
Re:Product Updates Based on Your Feedback by pilif on Wednesday September 26, 2018 @02:22AM (#18073208)
The cookies thing could be seen as a bug: the button does remove the cookies, but because your google sign in state is now tied to the browser sign in state, new cookies will immediately be set.

To fix this, the “remove cookies” button would also have to sign you out of chrome which would also feel weird from a UX perspective.

All in all I think this was just released a bit early before all UX edge cases could be tackled (or even discovered. Sometimes you find things only in wider rollouts)

Re:Product Updates Based on Your Feedback by cpeterso on Wednesday September 26, 2018 @02:58AM (#18073390)
If exempting Google's cookies from being cleared was a bug, they would not have added a message in the UI that "you won't be signed out of your Google Account":

https://twitter.com/ctavan/status/1044282084020441088

Re:Product Updates Based on Your Feedback by feanaro on Wednesday September 26, 2018 @07:07AM (#18074680)
> The cookies thing could be seen as a bug: the button does remove the cookies, but because your google sign in state is now tied to the browser sign in state, new cookies will immediately be set.

Then maybe tying the Google state to the browser state was a mistake and should be reverted?

Re:Product Updates Based on Your Feedback by theon144 on Wednesday September 26, 2018 @02:29AM (#18073237)
>A lot of our software's more complex interfaces are Chrome-first since its faster to develop - yesterday was the first time I made a serious consideration to change that approach.

Heh, I wonder if the next privacy blunder from Google will make you further reconsider your "voluntary vendor lock-in" approach :)

Re:Product Updates Based on Your Feedback by statictype on Wednesday September 26, 2018 @02:58AM (#18073393)
I said Chrome-first. Not Chrome-only.
Re:Product Updates Based on Your Feedback by reitanqild on Wednesday September 26, 2018 @03:15AM (#18073485)
I'd still ask to consider a Firefox first policy.

I've been using Firefox as my main dev browser for years and it has a huge, practical advantage:

- Usually it Just Works in every mainstream browser (had one single case in the last year where it broke in another browser).

My colleagues who use Chrome has to fix QA bugs more often than me it seems ;-)

Bonus: Support a good cause (cross browser compability)

Re:Product Updates Based on Your Feedback by wiz21c on Wednesday September 26, 2018 @04:40AM (#18073979)
yeah like in "this is just temporary code we put in production, we'll clean it later" :-) :-) </joking-with-a-touch-of-cynism>
Re:Product Updates Based on Your Feedback by feanaro on Wednesday September 26, 2018 @07:04AM (#18074659)
I disagree the sync thing was overblown. A website's cookies and the internal functionality of the browser are conceptually very different and (up to now) well differentiated concepts. Mixing them up and blurring the lines between them is just a portal to confusion of the average user, who is already confused enough.

I fear that changes like this will eventually make it impossible to effectively explain to an average user even the basics of how the web works.

Re:Product Updates Based on Your Feedback by Gaelan on Wednesday September 26, 2018 @10:59AM (#18076602)
Google's claim (which I'm inclined to believe) is that the previous state is more confusing to the average user. While we think in terms of "content" vs "browser", apparently the average user does not, and finds it confusing that part of the browser is signed into Google, but part isn't.
Re:Product Updates Based on Your Feedback by feanaro on Saturday September 29, 2018 @03:31PM (#18102303)
That may be, but that doesn't mean the concept should be abandoned and the browser married to the content in inexplicable ways. At least the way things are now, I am able to understand what is going on and teach it to my parents. If the non-average users also stop understanding what is happening behind the covers, is there any hope left for the open web?
Re:Product Updates Based on Your Feedback by dannyw on Tuesday September 25, 2018 @09:39PM (#18072003)
One nasty change was that clearing all cookies no longer cleared Google cookies with these changes. That is a big, privacy-impacting change.
Re:Product Updates Based on Your Feedback by judge2020 on Tuesday September 25, 2018 @09:54PM (#18072080)
I think that change was merited because of the "signed into chrome vs google" issue they were trying to solve. Say I clear my cookies on a signed-in, syncing account.

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 by eudora on Tuesday September 25, 2018 @10:33PM (#18072254)
Hang on.

The logical thing to do, if your real aim is to have browser sign in state reflect cookie state, is to sign out the browser when someone clears their cookies.

That would make total sense to users.

I think this is clear evidence that Google made this change to keep more users signed into Google so they can collect more of your data without telling you.

Re:Product Updates Based on Your Feedback by hn_throwaway_99 on Tuesday September 25, 2018 @10:56PM (#18072373)
The article says that is exactly what they are going to do now: when you clear all cookies, you will be signed out.
Re:Product Updates Based on Your Feedback by colordrops on Tuesday September 25, 2018 @11:40PM (#18072580)
What they are going to do. As currently released, it is a real issue, not some misunderstanding.
Re:Product Updates Based on Your Feedback by rhizome on Wednesday September 26, 2018 @04:01AM (#18073754)
Several people who make a lot of money figured it was a good idea.
Re:Product Updates Based on Your Feedback by eudora on Wednesday September 26, 2018 @02:18AM (#18073196)
Yeah we were talking about the pre-oh-shit-backtrack changes
Re:Product Updates Based on Your Feedback by bun_at_work on Wednesday September 26, 2018 @08:18AM (#18075099)
What data is it that Google collects without telling the user? Granted, they don't issue some pop-up notification or e-mail for every piece of data they collect, as the collect it, but every user has full access to all of the data points Google collects. They are highly transparent about the data they collect and even give users the option to delete that data from Google's records.

I could be mistaken, however, so I'm curious - what data does Google collect without telling the user, at least by making that data collection transparent?

Re:Product Updates Based on Your Feedback by Bekwnn on Tuesday September 25, 2018 @11:00PM (#18072387)
"Performing this action will log you out of chrome. (You may sign in again immediately afterwards.)"

Problem solved?

Re:Product Updates Based on Your Feedback by vincentmarle on Wednesday September 26, 2018 @12:16AM (#18072737)
It’s a dangerous precedent to begin with, I remember platform abuse was a serious concern when Google first launched Chrome. Over the years they’ve built up enormous trust by keeping Chrome (mostly) conflict-free. The moment Chrome really turns into “Google Browser” it will no longer be the default choice (although I suspect we may already be too late to undo this).
Re:Product Updates Based on Your Feedback by grey-area on Wednesday September 26, 2018 @01:10AM (#18072935)
So instead of putting in bizarre kludges in various parts of the UI fix the underlying issue - browser login should not be a prominent feature (it should be called sync bookmarks/history in settings somewhere), google logins should not be displayed in browser chrome and google websites should not get special treatment (either in cookies or login status).

That’s why people are complaining - they see that google clearly wants to privilege their own sites and logins in chrome and push the users to always be signed in with google across any site. Great for google, bad for user privacy and the open web.

Re:Product Updates Based on Your Feedback by theprotocol on Wednesday September 26, 2018 @03:05AM (#18073428)
> they see that google clearly wants to privilege their own sites

What happened to their very vocal concern over net neutrality from last year?

Re:Product Updates Based on Your Feedback by sizzle on Wednesday September 26, 2018 @12:26AM (#18072780)
"To us, it's clear that chrome sign-in is different from google sign-in, but to others, it may not be"

I highly doubt the common person knows what a cookie is, let alone how to clear them.

A simple solution would be to add an extra step when clearing cookies that asks if you would like to stay signed into your Google session and clear or keep those cookies based on your selection.

Re:Product Updates Based on Your Feedback by pythonaut_16 on Wednesday September 26, 2018 @06:26AM (#18074504)
The extent the common person (might) know about cookies is that sometimes it's helpful to clear them to speed up your computer and/or as part of other magical rituals.
Re:Product Updates Based on Your Feedback by feanaro on Wednesday September 26, 2018 @07:12AM (#18074714)
> To us, it's clear that chrome sign-in is different from google sign-in, but to others, it may not be.

But the fact that they are different things is precisely the reason why they should remain separate, not conflated into one soggy, confusing mess.

Re:Product Updates Based on Your Feedback by mivanov on Wednesday September 26, 2018 @12:20AM (#18072757)
It's Eric Lawrence and while I don't think he's off base, the disclaimer literally says he used to work on Chrome, so I don't think he is speaking as a competitor here.

Also, in my (admittedly, n=1) experience, Sync was enabled automatically, perhaps because I had tried it at some point.

Re:Product Updates Based on Your Feedback by vtail on Tuesday September 25, 2018 @09:32PM (#18071970)
Thomas, could you please explain the reference to arch-competitor - I might have missed any reactions by Mozilla/MSFT(?).

Thanks!

Re:Product Updates Based on Your Feedback by pmh on Tuesday September 25, 2018 @09:33PM (#18071975)
Eric Law works for Microsoft on Edge
Re:Product Updates Based on Your Feedback by hellofunk on Wednesday September 26, 2018 @03:26AM (#18073534)
And he also helped build chrome, so…
Re:Product Updates Based on Your Feedback by vtail on Tuesday September 25, 2018 @09:35PM (#18071981)
Thanks! Stupid me - that disclaimer was right at the top of his blog.
Re:Product Updates Based on Your Feedback by bangonkeyboard on Wednesday September 26, 2018 @06:13AM (#18074452)
> when your arch-competitor is speaking out on your behalf, maybe the narrative has gone a little haywire.

When the enemy of their enemy becomes their friend, the question then is who their common foe is. Microsoft is actively working to push the needle in the same direction as Google on ignoring and removing user choice in their products. An ex-Chrome dev at Microsoft defending dark patterns from his former team by mocking user concerns (as you are, with your "Matthew Green switch") is hardly an objective slam dunk.

Re:Product Updates Based on Your Feedback by afandian on Wednesday September 26, 2018 @07:02AM (#18074649)
I remember AOL and Compuserve back in the early 90s on Mac OS 7. They were online services, and they had something to do with the Internet, but it was a walled garden.

Google is free to do integrate their online environment into their client, but it's dishonest to continue to call it a web browser much longer.

Re:Product Updates Based on Your Feedback by x0x0 on Tuesday September 25, 2018 @09:37PM (#18071991)
This is what it looks like when product/eng inside google encounter a serious trust deficit.