News for hackers. Stuff that matters.
Re:Am I logged in or not? GDPR case study on the example of ... by svat on Monday September 24, 2018 @07:17PM (#18062314)
But this is only if you already have Chrome Sync ("logging in to Chrome") turned on and enabled, correct? Because I have a bunch of different Chrome profiles that I use for different purposes, and I don't see the ones that I use for particular Gmail accounts getting logged in to Chrome.
Re:Am I logged in or not? GDPR case study on the example of ... by daurnimator on Monday September 24, 2018 @07:19PM (#18062327)
(not a chrome user, but:) my understanding is that now if you log into google (e.g. a gmail account), you automatically get logged into chrome, including Chrome Sync.
Re:Am I logged in or not? GDPR case study on the example of ... by tptacek on Monday September 24, 2018 @07:30PM (#18062381)
That is not at all my understanding. If you don't have sync enabled, nothing automatically enables sync. You have to go through a large confirmation dialog (with an "undo" button) to enable sync.
Re:Am I logged in or not? GDPR case study on the example of ... by bigiain on Monday September 24, 2018 @08:01PM (#18062533)
Yet...</cynical mode>
Re:Am I logged in or not? GDPR case study on the example of ... by macintux on Monday September 24, 2018 @08:48PM (#18062713)
You’re being downvoted, but this is exactly the concern that a sweeping change like this provokes. Who’s to say Google won’t decide that a lack of sync is a problem they can silently fix too?
Re:Am I logged in or not? GDPR case study on the example of ... by tptacek on Monday September 24, 2018 @09:42PM (#18062917)
Who's to say they aren't going to backdoor Chrome to pop a shell on your box next time you search Google? Who's to say Mozilla won't do the same?
Re:Am I logged in or not? GDPR case study on the example of ... by reitanqild on Monday September 24, 2018 @11:25PM (#18063344)
The devil has enough advocates.

The turn on sync thing is already reported to be a dark pattern.

Also see: https://news.ycombinator.com/item?id=18062082

Re:Am I logged in or not? GDPR case study on the example of ... by tptacek on Monday September 24, 2018 @11:32PM (#18063372)
Yes, lots of people reported it to be a "dark pattern", but I'm very much with Nikita Borisov on this one:

https://twitter.com/nikitab/status/1044314072706158593

Meanwhile: whatever color you want to shade in the "pattern" with, this subthread starts with a claim that is falsifiable, and also actually false. So please don't pretend like I'm arguing from abstractions here.

Re:Am I logged in or not? GDPR case study on the example of ... by reitanqild on Monday September 24, 2018 @11:39PM (#18063399)
Thanks, I don't use Chrome that much (or at all if I an avoid it) so that's interesting.

Still there are the claims of buybackoff that I linked above that options has been set without their consent.

So it seems to me there's either a muddy pattern or they even are tweaking things on behalf of users whitout even asking?

Edit: also this from the post we are discussing:

> However, by clicking on “settings” I was unable to click “undo” - the user interface happily assumed that yes, in fact I wanted to first upload my data. And suddenly, instead of “Last time synced in 2017” I saw the following: “Last time synced on Today”.

Re:Am I logged in or not? GDPR case study on the example of ... by sizzle on Monday September 24, 2018 @07:32PM (#18062391)
Yeah my account was signed in and syncing when, prior to the update, I explicitly turned off sync so that was alarming to me. I immediately turned off syncing and now I can't trust Google to obey my settings anymore. They randomly turn on syncing when I use Google voice assistant on my Android phone.
Re:Am I logged in or not? GDPR case study on the example of ... by kevingadd on Monday September 24, 2018 @07:26PM (#18062357)
Yes, you automatically get logged into chrome. Supposedly sync will not automatically be enabled, but if you ever enabled it in the past it will be turned back on for your chrome session as well. It's unclear what happens to old (pre-login) history and cookies when this happens.