3 ms·
I've tried having this conversation, you're right. Making headway is really hard and one of the primary reasons is that the topic is very complicated. There a
by bradford 6y ago
I've tried having this conversation, you're right. Making headway is really hard and one of the primary reasons is that the topic is very complicated. There are many employees at MS who deal with those complexities as a full time job.
MS Devs who do venture to discuss it are aware of the complexities and tread very cautiously: any slight misphrase has bad outcomes. Smarter participants in the conversation will merely point you to Microsoft's public facing privacy statement, which is such broad legalese that it's not entirely helpful to the analytically minded individual that wants to learn more.
That said, I've worked with diagnostic data for several years now and I've never seen anything to justify the hatred that MS gets over this. I've been on teams that have spent a lot of effort ensuring that any data is gathered, stored, and used in a respectful and legal manner. I've seen mistakes, but they are disclosed and remedied as part of the business process.
[disclaimer, MS employee, my employer wants me to state that this is my opinion and not Microsoft's]
- ptx 6y agoBut there's a solution that's neither complicated nor complex, greatly reduces the effort required in the areas mentioned and virtually eliminates those mistakes: don't collect data from my machine. This solution has been successfully used before, even by Microsoft themselves! Note that you can still collect crash dumps and usage data (at the risk of reintroducing some of the problems solved by not collecting other people's data) if you just ask nicely (and clearly) and the user decides to allow it. Office and .NET used to do this.