3 ms·
While I do not disagree with your points, I would argue that it is more likely that this is a prime candidate for Hanlon's razor. The attribute substitution he
by T3OU-736 8y ago
While I do not disagree with your points, I would argue that it is more likely that this is a prime candidate for Hanlon's razor.
The attribute substitution heuristic makes ts easy to treat Microsoft as this single homogenous entity, but given its size and the diverse number of groups working on things, this diverse set of toggles of how to disable all the crappy ways in which they collect data is likely just a result of these multiple groups finding their own toggle a place in the settings panel.
Should they, as a company who has made loud noises claiming to care about user privacy (data centers in Ireland) be a lot better about disclosing everything they collect, _how_ they collect it, and ALL the ways to disable said collection mechanism(s)? Absolutely. But to assume that they do not do this because malice? Nah, incompetence due to low actual business priority of caring about end user privacy seems more likely.
- RickS 8y agoI 100% agree – I do not attribute this specific microsoft issue to malice. It's insanely hard to coordinate between teams at their scale, especially when feature ownership is partially shared in difficult-to-model ways. (I do attribute the misuse of "unlimited" by phone companies to malice, FWIW.) My point is more that microsoft, like any company, could implement processes to better catch this class of errors before they ship, but don't, because there are too few consequences for making mistakes, and so there's no incentive to improve prevention efforts.