Closed
Bug 1418784
Opened 8 years ago
Closed 8 years ago
default option regarding whether to install/update to not-yet-reviewed versions of addons
Categories
(Firefox :: Untriaged, defect)
Firefox
Untriaged
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: tozzedd, Unassigned)
References
Details
in bug 1418779, it's suggested to add an option allowing the user to specify whether they wish to restrict addon installs/updates to only the latest human-reviewed version released. this bug is to address whether or not this should be the default.
alright, so the following blog post documents a change to policy wherein addon's are now published prior to human review:
https://blog.mozilla.org/addons/2017/09/21/review-wait-times-get-shorter/
the benefit to this approach is that users will get updated versions of addons more quickly. whether that benefit is generally worth the weakened protection of users is the issue to be addressed by choosing the default.
to start with, the benefit may be overstated with respect to its utility. keep in mind that Firefox no longer even informs users when addons are updated (i.e. mozilla doesn't feel the updates even merit mention, yet is proceeding as if users are in a big hurry to see them); users are also very unlikely to follow the development of their addons to know about upcoming features in advance and to be so enthusiastic about possible new features that they feel a pressure to have the update a little earlier (by the way, how much lag, on average, is it estimated that the publish-before-human-review policy bypasses? a few days?). For such users, if the default ends up being to only install the latest reviewed versions, they could simply change the setting to suit their bleeding-edge preference.
in addition, isn't it already expected that review wait time will decrease going forward anyway (i.e. once the webextension transition settles out)?
Comment 1•8 years ago
|
||
Closing per resolution in bug 1418779.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•