|
|
|
|
|
by mikejb
1969 days ago
|
|
The (1) case is a bit inaccurate/misleading. From what I can gather from the article: - Gebru tweeted the name of the employee [1] - Axios then reached out to Google, who then made the following statement: > Our security systems automatically lock an employee’s corporate account when they detect that the account is at risk of compromise due to credential problems or when an automated rule involving the handling of sensitive data has been triggered. In this instance, yesterday our systems detected that an account had exfiltrated thousands of files and shared them with multiple external accounts. We explained this to the employee earlier today. Context matters. [1] https://twitter.com/timnitGebru/status/1351698317550432256 |
|
No, its not.
> Gebru tweeted the name of the employee
Sure, more to the point Gebru tweeted that Mitchell’s corporate email appeared to be nonfunctional, sure.
> Axios then reached out to Google
That seems likely to be the sequence of events, sure.
Usually and ethically, a company that was in exactly the circumstances Google described would have:
(1) Declined comment, or
(2) Confirmed the email was nonfunctional and declined further comment, or
(3) Explicitly declined comment on personnel matters (especially if the framing of the question from Axios raised the issue of it being a disciplinary action of some kind; raising a personnel issue when it wasn’t part of the framing of the question would itself be somewhat unusual.)
> Context matters.
As an abstract truism, sure; while the narrative you describe is exactly what seems like the most likely scenario to me, I didn’t describe it because that fact was already considered in the description of scenario #1. Google’s behavior is (even assuming that they are being completely honest) grossly unethical in the context described.