addons

https://github.com/mozilla/addons/issues/3145 Worth noting that the comment closing the issue mentions: > You can disable Google Analytics in about:addons by setting your Do Not Track status to on. > Again: this only affects users who visit the page with Tracking Protection on (which automatically enables DNT) or who manually set their DNT status to on. but Firefox removed the DNT control last month (https://bugzilla.mozilla.org/show_bug.cgi?id=1928087), though it kept the Tracking Protection control and privacy.donottrackheader.enabled is still available in about:config.

Mozilla is open to having an official dark theme for addons.mozilla.org, but the team working on AMO is too small and has no time for designing a new theme. They're accepting pull requests: https://github.com/mozilla/addons/issues/2193#issuecomment-2151006096 .

Mozilla has been recommending a copy-cat extension for ~3 years, despite reports from users and developers. https://twitter.com/Pythux/status/1154403982342852609 https://twitter.com/gorhill/status/1165747661691064322 https://github.com/mozilla/addons/issues/1078 This is an unpaid recommendation. Why would I trust Mozilla now that they’re getting paid?

It's pathetic to see the attitude demonstrated by Mozilla support on this. diox commented 4 hours ago I'm locking this like I did in #851 because no new information is being added. We're aware and we're working on it. This conversation has been locked as spam and limited to collaborators.[1] Bug 1548973 (armagadd-on-2.0) All extensions disabled due to expiration of intermediate signing cert NEW Unassigned (Needinfo from 3 people) Kevin Brosnan [:kbrosnan] We have confirmed this issue. Extra comments about this being broken will not advance this bug to being fixed.[2] Mozilla just left their entire user base unprotected against ads, trackers, and some hostile code. Then they insult their users. Undoing the damage is hard. First, they have to update their signing certificate. Then they have to re-sign all the add-ons. Then users have to rel

So why is this taking so long to fix? From https://github.com/mozilla/addons/issues/978 > diox commented 2 hours ago > I'm locking this like I did in #851 because no new information is being added. We're aware and we're working on it. I mean, two hours? WTF.

Mozilla is addressing the issue now. See https://github.com/mozilla/addons/issues/978#issuecomment-48...

Yes - see https://www.reddit.com/r/firefox/comments/bkcjoa/all_of_my_a... and https://www.reddit.com/r/firefox/comments/bk54mu/addonsexten... Cannot tell if it's related to https://www.reddit.com/r/firefox/comments/bjwz8n/addon_polic... (Says new Add-On Policy effective June 10th, 2019, so shouldn't be causing this. But...) As mentioned elsewhere, seems like when your clock hits 5/4 midnight UTC, you're done. I tried setting my clock in the past, but that did not fix the issue for me. (Clock was previously auto w/ daylight savings time enabled.) Super interesting to watch /r/firefox go from 3.8k active/online users to 5.6k over the past half hour... Edit: As mentioned below, there are GitHub/Bugzilla entries. They seem to be aware and starting to work towards a fix, though the explanation of the problem hasn't emerged yet. https://github.