2 ms·
I don't think we should conflate telemetry with general user data that can be sold. Seeing HOW a user uses an app (re your Spotify example) is useful for the de
by therealdrag0 8y ago
I don't think we should conflate telemetry with general user data that can be sold. Seeing HOW a user uses an app (re your Spotify example) is useful for the developers of the app. That is not data they are selling to other companies and IMO isn't a privacy issue and shouldn't negatively affect user experience.
What theme you use or what buttons you click most often, isn't sellable; what is sellable are interests, consumables, and demographic distinguishers.
- inetknght 8y agoSeeing HOW I use an app can be a perceived privacy issue. It definitely can negatively affect user experience. Case in point: limited bandwidth and/or high latency, especially if the telemetry is transmitted with synchronous communication. What theme I use is sellable, especially if themes can be purchased. What buttons I click most often is also sellable by making it known what features would attract the most advertisements or what kind of data drives my use of the application.
- therealdrag0 8y ago1. Personally I think telemetry is worth its weight in byes. If you don't have enough bandwidth to load media, that can reduce UX on most sites, but that's your problem and doesn't affect most target audiences. If you're streaming audio on Spotify the telemetry bandwidth is unlikely to get in the way. 2. I think there's still a distinction. Using telemetry to better monetize the product your using is different than selling data to a third party to target you. Back to your original post though, I do agree that you should be able to opt out of any and all data collection. This already is a pattern too, you often see the "allow us to collect diagnostic information" dialog in software.