search

ankidroid / ankidroiddocs

AnkiDroid Documentation
GNU General Public License v2.0
49 stars 51 forks source link

docs: prepare 2.16.5 changelog #115

Closed mikehardy closed 1 year ago

mikehardy commented 1 year ago

I really struggled with how to explain the analytics lapse

My goal was to accurately describe

I'm open to any changes on any of it as long as they generally satisfy the goals above and sound like a human vs some person reading or writing a fake apology from a script

david-allison commented 1 year ago

I believe (needs confirmation) this was only triggered if the user opened their settings AND a default from an old version hadn't been set

mikehardy commented 1 year ago

related thought - just putting this here before I forget about it - perhaps we should rename the analytics opt-in key in a future 2.17 release, and make it such that the new key is checked for opt-in-ness so this old key which now perhaps has some corrupt data on device from incorrect defaults is ignored? Basically just wipe the opt-in-ness clean.

Our decision-making on analytics is based on percentages of devices reporting that use a feature - not absolute counts, so this would radically lower the number of devices reporting, to start, but I do not believe it would affect any decisions we would make about feature usage in the future, and it would demonstrate a commitment to opt-in by never using the potentially corrupt setting 🤔

(technically - it could connect to a completely fresh analytics property and everything, just throwing the old one away - we don't do anything custom that I'm aware of, no value lost...)

mikehardy commented 1 year ago

I believe (needs confirmation) this was only triggered if the user opened their settings AND a default from an old version hadn't been set

I think you're right, but if it's possible - even a tiny crack of possible - it's a trust issue, and if we can make it a zero percent chance, I'd like it...

david-allison commented 1 year ago

I'd support renaming the key + opting everyone out by default.

EDIT: in this release, or a future patch if we want this out the door ASAP

david-allison commented 1 year ago

My note was only that the unintentional opt-in definitely WILL have occurred and it shouldn't, but the impact was more limited than 'analytics is opt-out by default'