Freedom issue #2409

[iceweasel] Can recommend non-free extensions and themes on about:addons page

grizzlyuser - 13 days ago - . Updated 3 days ago.

freedom issue
% Done:



Firefox 68 introduced extension recommendations in about:addons page [1].
Description of the recommendation program [2] doesn't say they require the extension to have libre license in order to get recommended.

In the list of recommended extensions [3] I found a few which don't look like free ones:
[4], [5], [6]. Here's a quote from [6] that restricts freedom to distribute modified versions:

Derived works using source code that serve the same general purpose as
the original software may not be distributed using any official Mozilla
services such as or through any other official
service for any web browser without prior permission. Works using
portions of source code for other purposes may be distributed without
this restriction.

There's also
a similar program for themes [7]. Here's an example of recommended theme that has Creative Commons Attribution-NonCommercial-NoDerivs 3.0 license [8]. If I understand correctly, that license cannot be considered to be free.


That's why it looks like Iceweasel needs to be patched in order to disable or remove the offending functionality.




Updated by bill-auger 13 days ago

  • Priority changed from bug to freedom issue
  • Status changed from unconfirmed to confirmed

this was noted a few days ago in issue #2318

it is controlled at least partially by the 'extensions.htmlaboutaddons.recommendations.enabled' config key


Updated by CommodoreCrunch 12 days ago

facepalm I totally didn't notice the separate "recommendations" menu. I only saw the section below my installed extensions.

I tried setting "" to false, and clicking "recommendations" now falls back to loading the GNU IceCat wiki page instead. So that seems to do the trick.


Updated by grizzlyuser 11 days ago

I'd like to notice that I have not reported this issue to Mozilla yet (didn't have much time for that). IMO it is necessary to try to resolve all freedom issues upstream first. Not sure though if Mozilla is going to resolve this, for example by excluding non-free things from recommendations. If by any chance anybody has an idea what's the best way to communicate about this particular issue to Mozilla, please let me know, or feel free to report it yourself.


Updated by grizzlyuser 3 days ago

I've asked staff about this issue, please find the entire conversation attached. So it looks like that won't be resolved by Mozilla.

Also available in: Atom PDF