I can see why they thought this was a good change. It makes the UX for G-suite apps much more pleasant, almost like you get the full functionality of G-suite productivity stuff as part of installing Chrome. For most people, that's a good thing. I think as tech people we systematically tend to under-think the second-order effects of the systems we build. Case in point, Chrome and G-suite being that closely integrated…
I can see why they thought this was a good change. It's a good change only if you are permanently logged in to google services, which is probably why it seemed like a great idea to the Chrome team, who probably have no idea how much distrust Google has started to build up. It moves the browser closer to an app runner for google services - I'd understand that if this was on Chrome OS or a specific 'Google' app, but in…
Am I logged in or not? GDPR case study on the example of Chrome browser change
221–230 of 507 posts
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#222Earlier quoted context omitted.
There is a process where external launches need to be approved by a separate privacy team. If you're certain you can do a better job, you can find some listings on https://careers.google.com/ (just search for privacy).
I don't think that using this incident as a recruitment pitch is a good idea.
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#223Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#224Earlier quoted context omitted.
I can see why they thought this was a good change. It's a good change only if you are permanently logged in to google services, which is probably why it seemed like a great idea to the Chrome team, who probably have no idea how much distrust Google has started to build up. It moves the browser closer to an app runner for google services - I'd understand that if this was on Chrome OS or a specific 'Google' app, but in…
Just use different browsers for different things man, this isn't even hard. I seriously do not understand the outrage over this. Half the websites we visit host their fonts on Google domains, where is the outrage over that?
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#225Are there any lawyers here who can tell us if this is actually a GDPR violation? Most of the discussion here is about why people don't like the new Chrome feature -- but is it actually in violation of the GDPR?
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#226Earlier quoted context omitted.
That's a bad example. In technical progress, Chrome is the complete opposite of IE (which seems to be replaced by Safari these days) and way better than the rest in pushing forward new features. Also 99% of the time Firefox and Edge work just fine. EDIT: Yes, IE was great in the beginning, but then it stagnated and earned the wide reputation of being terrible obsolete anchor that it is now known for. It's with this l…
IE at its core was technically very advanced, way faster than Netscape, and pushed a ton of new features. Dynamic HTML as it was called, CSS, encryption, and so much more stuff came to IE before any of the competitors. Then it became the IE6 we all came to know. The analogy with Chrome starting as a trail blazer and progressively taking the same trajectory is perfect, really.
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#227Earlier quoted context omitted.
But the tech-savvy community has influence. We set up computers for our friends and families. We write IT policies. We are web developers, tech reporters, and more. At least for me, Google's behavior means that I can no longer recommend Chrome.
I can't imagine the impact is significant even if we consider two degrees of acquaintances (you tell someone to not use Chrome and they tell someone else).
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#228Chrome has been the new IE for years. "just use chrome" is an endless refrain from webdevs who don't want to test on Firefox. Not sure why it is so hard for people to see what is going on here. Google has a massive conflict of interest with their web development efforts. This is classic Microsoft-esque Embrace, Extend, Extinguish.
Not at all. I used to start developing while netscrape was still a thing. Chrome is (and it was) a bless for developers. I try firefox like once a year and see no reason to switch.
THe actual case is also no reason to switch (for me) but ill watch it.
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#229Earlier quoted context omitted.
If Bob logs into Alice's computer and forgets to log out all she has to do is hit the "sync" button and she can now view everything that's his synced with his account. Previously she would have at most his email, now she has that and more. To me that seems like a decrease in privacy.
I don't want to get too far into specifics because I'm not an expert, but I'm pretty sure there are a number of inaccuracies in this comment. Notably, synced data would have been visible in myaccount.google.com already, and if he had syncing disabled, I don't think there wouldn't be any data synced with his account to view. In other words, assuming Alice was nefarious, yes this is still terrible, but I don't think it…
That makes no sense at all unless syncing is an account wide setting instead of a browser setting, and it's pretty clear that this is a browser setting. Bob could have syncing enabled on his primary computer, log into gmail on Alice's computer where it then logs him in to her browser but without syncing enabled, and then Alice can later on come in and enable syncing by hitting the blue button.
Frankly it sounds like what Google should have done is created a better security system rather than a better notification system. This solves nothing, creates more problems, and pisses people off at the same time.
Re: Am I logged in or not? GDPR case study on the example of Chrome browser change
#230Earlier quoted context omitted.
>How is sending my personal passwords to a server under Google's control an increase in my privacy? If this change did that, I might be inclined to agree with you. But as far as I know, it doesn't. You still have to explicitly opt in to syncing. Which is a no-op compared to the old behavior.
According to the Privacy Policy (even after the changes from this weekend) this change gives Chrome permission to upload data. > The personal information that Chrome stores won't be sent to Google unless you choose to store that data in your Google Account by signing in to Chrome. If what you are saying is true- and will remain true for the future- why didn't they change that language to say something like- > The per…
[1] https://www.google.com/chrome/privacy/#signed-in-chrome-mode