Extension Manager:Update Checking: Difference between revisions

 
Line 174: Line 174:
The privacy policy almost certainly needs some tweaks but as well as that the main identified issue is that there is no simple means for a user to stop sending information about installed add-ons to AMO through the metadata checks and discovery request. {{bug|635115}}
The privacy policy almost certainly needs some tweaks but as well as that the main identified issue is that there is no simple means for a user to stop sending information about installed add-ons to AMO through the metadata checks and discovery request. {{bug|635115}}


There are a few different options that we may want to consider for Firefox 4, none of them are particularly ideal I think:
We should change to the following:


# Stop setting (3) from removing add-ons from the list sent in the discovery request
* Setting (1) should turn off the following requests as they are background, non-user-initiated requests:
# Use setting (4) to disable including add-on information in the discovery request and create new UI for it somewhere. This is probably a non-starter due to the need for new UI plus it just creates yet another user-visible option.
** Background update check
# Use setting (4) to disable including add-on information in the discovery request and make the existing UI for setting (2) control setting (4) as well.
** Background metadata check
# Use setting (3) to disable including information in the discovery request. I dislike this option as it really is mixing up the point of setting (3).
* Setting (4) should turn off the following as they potentially expose private information:
# Use setting (4) to disable including add-on information in the discovery request and don't have any UI for it at all, users that need to stop sending the information globally will have to go to about:config to do it.
** Background metadata check
# Don't include the information in the privacy policy on how to turn off transmitting the information.
** Install time metadata check
 
** Including add-ons in the discovery request
The question is how serious do we consider this issue and how much do we think users need primary UI to control it?
* Only setting (5) should control whether a single add-on is included in the background metadata check, install time metadata check and the discovery request
canmove, Confirmed users
1,570

edits