Gandalf_The_Grey
Level 85
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
- Apr 24, 2016
- 7,875
Best quote in this article:Companies build software products. They release said software products into the wild. People start using them, and sometimes, there be problems. But how can companies really know that their products are working as expected? User interaction? Unreliable. Some form of automated mechanism that tracks software usage and reports data back? Yes.
Software telemetry is a relatively transparent way of collecting data about human-software interactions, with the noble goal of improving software products. Alas, if only the reality was so cuddly and naive. As it happens, humans quickly realized that data collected in this manner can be used for more than just improvements in the product. And thus, overnight, a noble goal became ignoble. So the question is, should you, as an end user, allow, encourage or accept telemetry in the software you use?
Read the full article here at Dedoimedo:The longer the data exists out there, the probability of it being leaked out approaches one.
Should you allow telemetry?
Article discussing the pros and cons of data telemetry in software products, including functional and financial objectives, indirect and direct data analysis, personal and non-personal data, privacy implications, data leaks, product quality, and more