3 ms·
"Good on Google for (apparently) taking appropriate corrective action in this case." Considering: (1) this is the same India contractor that was involved in t
by Steko 15y ago
"Good on Google for (apparently) taking appropriate corrective action in this case."
Considering:
(1) this is the same India contractor that was involved in the scandal last week.
(2) The new infractions happened after that scandal broke.
(3) As far as we know they are still giving their business to this contractor.
Then you have to seriously doubt whether "appropriate corrective action" has been taken.
- dredmorbius 15y agoWell: 1: If this is the case, Google have correctly identified the source and it turned out to be the same in both cases. 2: Mocality broke on Friday. The OSM incidents were reported Monday, and apparently had been ongoing for at least a few days prior. I'd say they're largely coincident. 3: It does take some time for a business to respond, especially where contractual issues are involved. I suspect in this case the OSM report was a final straw / accelerator in Google's decision process. Speaking for myself, I used the term "apparently" as we've just got Google's report of their action, I haven't seen it verified elsewhere. Though I'd be inclined to believe their statement (lying at this point would be a Really Dumb Move[tm]). Really, given the scale of operations, this is lightning action on Google's part. As I noted, the problem here is that there are three incidents (two tied to the same contractor) of malfeasance in Google's name (if indirectly, through contractors, on Google's part). This speaks to shoddy practices, or in best light, considerable room for improvement.
- Natsu 15y agoThe update to the article addresses items 1 & 3, claiming it's the same IP, but not the same people. Apparently two people made about 20 troll edits to OSM. They've been fired for abusing Google's network policies.