Should allowing FF remote control over extensions (restricted ones) be disabled by default on Librewolf

pre-requisites

  • I've read and followed the contribution guidelines;
  • I've reproduced the issue in a new LibreWolf profile;
  • I've checked that the problem is not present in a stock Firefox profile;

details

  • browser version & OS: librewolf 115.0.1-1, artix gnu+linux
  • steps to reproduce: n/a
  • expected result: extensions.quarantinedDomains.enabled set to false by default on Librewolf
  • actual result: extensions.quarantinedDomains.enabled is not set by Librewolf, therefore the FF default of true applies
  • console errors and warnings: n/a
  • others: n/a

I'm wondering if Librewolf should be setting extensions.quarantinedDomains.enabled on librewolf.cfg, and with false value, so that unless overwritten by the user, Librewolf disables that behavior by default. You can read more from mozilla about it on its blog Why are some add-ons not allowed on sites restricted by Mozilla?, and more about remote control over extensions on its bug Implement a Remote Settings for the Quarantined Domains pref, and see some negative reaction on the blog Firefox 115 can silently remotely disable my extension on any site.

Having some remote agent having access to the sites I'm accessing, and controlling the extensions I use on it (most of them are privacy oriented ones), seem definitely the wrong path to follow. I'm surprised FF is doing this, :(. There's a post placed on lemmy.ml/c/librewolf, to discuss about the convenience and privacy issues with the feature, present on FF 115 and beyond, but it seems devs are paying less attention to lemmy these days (one or two were paying attention to it before), :).

Thanks !

Edited by Javier