canmove, Confirmed users
1,570
edits
Extension Manager:Update Checking: Difference between revisions
Extension Manager:Update Checking (view source)
Revision as of 02:58, 18 February 2011
, 18 February 2011→Potential Improvements
| Line 170: | Line 170: | ||
This implies to me that turning Off Automatic Updates, setting (2), will not transmit the listed information. This is currently correct because we included setting (3) in the background metadata check controls however as noted above I'm not sure that was the right thing to do. Again setting (1) does control this. | This implies to me that turning Off Automatic Updates, setting (2), will not transmit the listed information. This is currently correct because we included setting (3) in the background metadata check controls however as noted above I'm not sure that was the right thing to do. Again setting (1) does control this. | ||
=Potential Improvements= | =Potential Improvements for Firefox 4= | ||
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: | |||
# 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. | |||
# 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. | |||
# 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). | |||
# 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. | |||
# Don't include the information in the privacy policy on how to turn off transmitting the information. | |||
The question is how serious do we consider this issue and how much do we think users need primary UI to control it? | |||