4 ms·

I bet you also want the software to work and not have bugs. Telemetry gives devs information to prioritize and debug information fix the bugs.

cwhiz 6y ago
You can... 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.
- m463 6y ago
  > Make telemetry opt-in and ask the user to share data. This is what Apple does You should check - apple software still contacts the mothership constantly.
type0 6y ago
By that reasoning Enterprise edition of Windows is worse because users actually can turn the spying off
rumanator 6y ago
>>I bet you also want the software to work and not have bugs. Telemetry gives devs information to prioritize and debug information fix the bugs. 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.
ric2b 6y ago
And yet, if anything, I see an inverse correlation between software quality and invasive telemetry. Maybe there's a correlation between invasive telemetry and not caring about your users.

4 ms·

I bet you also want the software to work and not have bugs. Telemetry gives devs information to prioritize and debug information fix the bugs.

by haecceity 6y ago

cwhiz 6y ago
You can... 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.
- m463 6y ago
  > Make telemetry opt-in and ask the user to share data. This is what Apple does You should check - apple software still contacts the mothership constantly.
type0 6y ago
By that reasoning Enterprise edition of Windows is worse because users actually can turn the spying off
rumanator 6y ago
>>I bet you also want the software to work and not have bugs. Telemetry gives devs information to prioritize and debug information fix the bugs. 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.
ric2b 6y ago
And yet, if anything, I see an inverse correlation between software quality and invasive telemetry. Maybe there's a correlation between invasive telemetry and not caring about your users.