As for why this matters, you need only look at Hong Kong for that answer. And even here in the US, many large companies are kowtowing to the Chinese government and changing their products in the US to toe those lines.
As for why this matters, you need only look at Hong Kong for that answer. And even here in the US, many large companies are kowtowing to the Chinese government and changing their products in the US to toe those lines.
I think that it's incorrect to believe that telemetry allows developers to build "better" software. Web pages have had intrusive telemetry for over a decade now, and they still broadly suck. We're able to navigate the world of hamburger menus, text with poor contrast, and scrolljacking because we're adaptable humans, not because these kinds of changes actually improve the websites.
The problem is that telemetry can only tell you the "what" and "how", but not the "why".
> If you trust the developer
It's not just the developers who gain access to that data. It's everybody at the company. It's 3rd parties who contract with that company. It's everybody who hacks into the data set at the company. And it's every governmental agency from (almost) any country with an overly broad warrant who has access to that data.
See my upstream comments about China and Hong Kong
> No one is making you use that software.
Just as nobody is making an effort to make it simple (or even possible) to make an informed choice about whether I should use that software. Homebrew is a great example. I know that it's sending telemetry to Google only because someone raised a ruckus and used social pressure to make the homebrew devs add in a reasonable amount of consent into the install and update process.
Thankfully, laws are catching up with technology, and I should soon be able to rely upon simply saying "data collection not directly tied to software functionality legally requires my explicit consent, and that consent is not required to run the software".
1. Did this error condition that should not happen happen?
2. How many users did it happen for? (Who is not available for legal reasons)
If you search for tracelogging in the code you'll find they're associated with debugging and errors.
https://github.com/microsoft/winget-cli/blob/e997f3e394e66f2...
I don't know if you understand how difficult it is to debug programs that fail on someone else's machine. Well that's what telemetry is for.
1. Make telemetry opt-in and ask the user to share data. This is what Apple does
2. Collect telemetry and give the user an option to share that data after a crash or bug. Many companies do this.
3. Make telemetry opt-out but be forthright with what information is sent and why.
4. Don't allow opting out of telemetry but be open and upfront with what is being collected and why.
5. Hide the fact that telemetry is being sent, hide what is being sent, and don't allow the user to opt out.
You should check - apple software still contacts the mothership constantly.
You're just illustrating a single possible use among the universe of actual real world uses of telemetry, such as gathering your personal info to build up your profile to use against you as the company sees fit.
As others have stated throughout this discussion, it's standard practice for over a decade to use systems that don't collect telemetry to keep systems updated and safe. It boggles the mind how some people try to claim that the only way to remain safe with Microsoft products is to be perpetually spied upon.
Maybe there's a correlation between invasive telemetry and not caring about your users.
Says who?
I'd even go so far as to say "Common Sense".