4 ms·

What's so sad about this is that no one will ever get slapped for this. Not rank-and-file people that coded this, not the people who green-lit this, not the ass

by mszcz 6y ago

What's so sad about this is that no one will ever get slapped for this. Not rank-and-file people that coded this, not the people who green-lit this, not the asshole claiming this is a "programming error", not anyone. 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.

shadowgovt 6y ago
Why do you assume it isn't a programming error?
- mszcz 6y ago
  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?
  - burnerfi5724 6y ago
    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/+/f800edbd1b50ecc13a0d3391f5f45ba9c84625be%5E%21/#F0 https://chromium.googlesource.com/chromium/src.git/+/f800edb... I'll let you judge for yourself, but this is not coming from PR.
    - _qulr 6y ago
      Thanks for the link!
  - shadowgovt 6y ago
    > 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.
bichiliad 6y ago
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.

by mszcz 6y ago

shadowgovt 6y ago

Why do you assume it isn't a programming error?

mszcz 6y ago
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?
- burnerfi5724 6y ago
  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/+/f800edbd1b50ecc13a0d3391f5f45ba9c84625be%5E%21/#F0 https://chromium.googlesource.com/chromium/src.git/+/f800edb... I'll let you judge for yourself, but this is not coming from PR.
  - _qulr 6y ago
    Thanks for the link!
- shadowgovt 6y ago
  > 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.

bichiliad 6y ago

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.