3 ms·
Relevant context: https://bugzilla.mozilla.org/show_bug.cgi?id=1548973#c57 https://bugzilla.mozilla.org/show_bug.cgi?id=1548973#c57 > Update: We have rolled o
by whym 7y ago
Relevant context:
https://bugzilla.mozilla.org/show_bug.cgi?id=1548973#c57 https://bugzilla.mozilla.org/show_bug.cgi?id=1548973#c57
> Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.
Further context: https://news.ycombinator.com/item?id=19823701 https://news.ycombinator.com/item?id=19823701
- user17843 7y agoThis partial fix via Normandy means a relevant part of the user base may still be in the dark: tech-savvy power users with many extensions who have chosen to disable normandy. (This is probably also the group which is most affected by reset extension settings)
- tux3 7y agoIndeed, I had opted out of Normandy, SHIELD studies & co after the Looking Glass/Mr. Robot promotional ad fiasco. Tentatively re-enabled, it's now 2 hours since the announcement but I haven't received the preference flip study yet. A couple more hours before my fox's lastUpdateTime rolls around and my extensions get disabled, patiently waiting to see if I'll have to take manual action! Edit: Funny, my app.normandy.run_interval_seconds was set to 24h for some reason, the new default seems to be 6h. I wonder how many people are also in that situation.
- bwat49 7y agoI found that setting app.normandy.first_run to true and then restarting firefox triggers the hotfix study to be installed (and the pref then automatically sets itself back to false)