Kindle collects a surprisingly large amount of data

Post by thdrdt » Tue, Aug 25, 2020, 2:33 PM UTC

jacquesm wrote: post #95

Despoisj wrote: post #38

As a former Kindle developer, I can say that most of what's mentioned in this article are metrics used to understand how the features are used (bookmarks, highlights, dictionnary, etc.), how much they are used, and in which country. This allows the teams to focus on features that are actively used, and sometimes lead to discontinuing features that see little to no use. Hope that helps.

It doesn't really matter does it? You don't collect data without consent, period. Why is that so hard to understand? Why don't developers ever push back against this sort of thing? Collectively we build this stuff, we are not 'soldiers following orders' which makes us responsible for what we create. The current actual use is not relevant. Consent and the possible uses are relevant.

Post by jjcon » Tue, Aug 25, 2020, 2:35 PM UTC

neiman wrote: post #123

jjcon wrote: post #111

Earlier quoted context omitted.

Whether you like it or not this collection does lead to better products - that is why you think every company does it because those that don’t usually die out. Understanding your users is vitally important. Privacy LARPers are a tiny segment of the market, the average person doesn’t really care if their ‘usage of the highlighter function is tracked’

> Privacy LARPers are a tiny segment of the market, the average person doesn’t really care if their ‘usage of the highlighter function is tracked’ If so, why don't they loudly advertise the data collection and do it only with opt-in? It's not that the average user doesn't care if they're tracked, it's that they're not aware that they're being tracked.

Post by [deleted] » Tue, Aug 25, 2020, 2:37 PM UTC

jjcon wrote: post #118

gvjddbnvdrbv wrote: post #106

Earlier quoted context omitted.

There are some features in software I rarely use. But those times I do use them they are utterly essential. If I find such feature has been removed I am incensed. Usefulness is NOT the same as usage.

> Usefulness is NOT the same as usage. Metrics can tell that story though so you’re arguing a straw man. Example: If you see that 99% of users have never used a function ever - you have a pretty good idea that it needs to be reworked or removed. You may also see a function that is used by 80% of users once a month, that you may opt to keep.

Post by gvjddbnvdrbv » Tue, Aug 25, 2020, 2:37 PM UTC

mikro2nd wrote: post #134

gvjddbnvdrbv wrote: post #112

Earlier quoted context omitted.

Only a matter of time before devices come with 5G data connections...

...which would require a valid SIM. So just don't add one. If the device comes with a pre-inserted/hardwired/virtual SIM, well... several countries in the world require KYC-style registration of the SIM owner before networks are allowed to activate the SIM, so there'd still be an opt-out path for the user in such countries. eta: My point being: Now you're in a twisty little maze full of corner cases, all different. N…

Post by hans_castorp » Tue, Aug 25, 2020, 2:38 PM UTC

jacquesm wrote: post #95

Despoisj wrote: post #38

As a former Kindle developer, I can say that most of what's mentioned in this article are metrics used to understand how the features are used (bookmarks, highlights, dictionnary, etc.), how much they are used, and in which country. This allows the teams to focus on features that are actively used, and sometimes lead to discontinuing features that see little to no use. Hope that helps.

It doesn't really matter does it? You don't collect data without consent, period. Why is that so hard to understand? Why don't developers ever push back against this sort of thing? Collectively we build this stuff, we are not 'soldiers following orders' which makes us responsible for what we create. The current actual use is not relevant. Consent and the possible uses are relevant.