Re:When you tell Chrome to wipe private data it spares Googl...
by bichiliad on Tuesday October 20, 2020 @02:18PM
(#24840656)
I think punishing one person (or even a group of people) is an ineffective tool. If someone gets fired for this, maybe we'll feel better, but I'm sure the cumulative tracking data would be worth it, and it wouldn't change their motivations for doing these sorts of things. It's similar to punishing an engineer for pushing a commit that causes an outage. They didn't come to work planning on an outage, and they probably didn't think they were going to cause an outage up and until the outage happened. If you fire them, you're doing nothing to prevent that outage from just happening again with someone else later.
Re:When you tell Chrome to wipe private data it spares Googl...
by shadowgovt on Tuesday October 20, 2020 @12:46PM
(#24839556)
Why do you assume it isn't a programming error?
Re:When you tell Chrome to wipe private data it spares Googl...
by mszcz on Tuesday October 20, 2020 @01:33PM
(#24840135)
1. It's next to impossible to make a mistake like that.
2. The mistake works out in Google's favour.
3. Difficult to give Google the benefit of a doubt anymore regarding anything.
4. Does anyone believe what PR dept. of a large corporation says anymore?
Re:When you tell Chrome to wipe private data it spares Googl...
by burnerfi5724 on Tuesday October 20, 2020 @02:59PM
(#24841118)
One benefit of this being chrome.... is the changes are public.
Here is the fix and the link the cl for the fix with a link to the cl that created the issue as well: https://chromium.googlesource.com/chromium/src.git/+/f800edb...
I'll let you judge for yourself, but this is not coming from PR.
Re:When you tell Chrome to wipe private data it spares Googl...
by _qulr on Tuesday October 20, 2020 @04:29PM
(#24842048)
Thanks for the link!
Re:When you tell Chrome to wipe private data it spares Googl...
by shadowgovt on Tuesday October 20, 2020 @03:32PM
(#24841459)
> It's next to impossible to make a mistake like that
It would appear that the root of this error is that Chrome is also an operating system. So in small, focused apps, yes, that's a hard mistake to make. In apps that some people are using as the main shell for their entire laptop, there's a lot of nooks and crannies for complexity to hide.
I know it's easy for those people to claim that they didn't know what they were doing or that they were told that it's fine. But maybe slapping a few would cause others to finally fucking think for a moment "do I wanna go to jail over this?". If you're making decisions that affect the privacy of literally millions of people then, well, maybe you need a little accountability.