canmove, Confirmed users
1,448
edits
User:Jorge.villalobos/WorkWeek2012Q2: Difference between revisions
User:Jorge.villalobos/WorkWeek2012Q2 (view source)
Revision as of 19:58, 13 June 2012
, 13 June 2012→Blocklisting
| Line 37: | Line 37: | ||
===Blocklisting=== | ===Blocklisting=== | ||
* The blocklist should be hardened by moving it to a separate process. I think this can be done relatively easily on Windows because of the changes done for Silent Update. It should be still be possible to configure it, but not with Firefox preferences that can be easily changed by extensions. | * The blocklist should be hardened by moving it to a separate process. <strike>I think this can be done relatively easily on Windows because of the changes done for Silent Update.</strike> It should be still be possible to configure it, but not with Firefox preferences that can be easily changed by extensions. | ||
** How it ultimately interacts with the Add-ons Manager is still a vulnerable area, though. | ** How it ultimately interacts with the Add-ons Manager is still a vulnerable area, though. | ||
* Change the refresh rate to twice a day to improve its effectiveness. | * Change the refresh rate to twice a day to improve its effectiveness. | ||
| Line 47: | Line 47: | ||
** It should be possible to link to a more detailed article about the problem. | ** It should be possible to link to a more detailed article about the problem. | ||
** This will significantly improve our ability to deal with quality problems in add-ons. We want to avoid user fatigue (too many warnings), but it should significantly lower the bar for dealing with bad situations. | ** This will significantly improve our ability to deal with quality problems in add-ons. We want to avoid user fatigue (too many warnings), but it should significantly lower the bar for dealing with bad situations. | ||
===Add-on Quality=== | ===Add-on Quality=== | ||
* The solutions proposed in the Add-on Security address some of this, by offering (or mandating) code reviews for non-AMO developers. | * The solutions proposed in the Add-on Security address some of this, by offering (or mandating) code reviews for non-AMO developers. | ||