This is AFTER debloating all the MS bs as much as I can.
The amount of MS telemetry is just mindboggling.
Well blocking these calls obviously inflates the numbers due to retries.
While telemetry is bad the problem here is probably that this windows service pings the server but doesn’t get a response because it got stuck in your pihole. So it tries to pings again and again and again and again…
Devil’s advocate: basically the only proper way to figure out how people are using your product and how you can tweak it to achieve its goal is by firing events and including relevant metadata such as how much time they spent on a screen or how far they scrolled. Telemetry is not necessarily “evil” by default.
I recently switched my main desktop from windows to linux, and now my download speeds are much faster. I guess now I know why. 😬
As someone who has designed and used telemetry systems, I’ll never quite understand the strong aversion some people have to them. Telemetry is what lets me tell my boss “yes people really do use our software this way and we can’t break it” or “90% of crashes happen right after the player uses a grenade”. And despite what some conspiracy theorists would have you believe, telemetry data for software from reputable companies does not get sold or used for marketing purposes. Our lawyers make sure of it, and also make us go through privacy reviews to make sure that data isn’t leaking PII.
As a programmer: “your data is boring. I am not interested in leveraging this for anything besides getting the service you are using to work as well as possible”
Also me as a programmer: “yo, you don’t need that data, stop asking for it. Ohh, your app is broken because it can’t access permissions? Yeet.”
It’s not about what the programmers want, it’s about the sales and marketing departments. They are the ones who use and abuse that data
As a UI designer, no it’s not just them. We need to know how people are using features to know if we should prioritise or deprioritise work on them and what work we might want to put in them.
We need to know how people are using features to know if we should prioritise or deprioritise work on them and what work we might want to put in them.
So ask them to take the survey, instead of spying on them.
