Is this also present on Librewolf? Or is it removed?
I don’t like someone having remote control over what I’m using, and this seems to have some of it, according to Bug 1832791 - Add to AMRemoteSettings support for quarantinedDomains RemoteSettings entries.
If not removed completely, perhaps it can be a default config option on Librewolf, taking advantage on the opt-out made available through extensions.quarantinedDomains.enabled.
I don’t know the implications on “security” by opting out, but for sure I don’t want any of my chosen privacy extensions to be shut down for any specific site, even if it’s not monitored by FF or whatever. Also, who decides what’s insecure for which sites? Is there a Librewolf say about this “feature”?
More about it from Firefox 115 can silently remotely disable my extension on any site.
Edit:
Two issues were filed about this (already closed), Should allowing FF remote control over extensions (restricted ones) be disabled by default on Librewolf , and some work before v115, which are fixed on 115.0.1-2, through commit 2c561ca85dbf791d83da41ffab829afca8b19323, but not yet fixed on 115.0.1-1…
Yeap, I was aware of the option on FF. I’m wondering what’ll be the default behavior on Librewolf, which is what I use (certainly saner defaults than FF ones).
@kixik If you are interested, you can look it up at about:config.
I use Librewolf from non official Artix repo, but mantained by an Artix dev, and its current version is 114.0.1, one minor version behind the AUR one, which currently is 114.0.2. So I can’t confirm on any 115* Librewolf version…
This community used to have representation from Librewolf devs, but it’s been a while since I don’t see much from them. It was really handy having them around…
@kixik I have looked it up and it is not set by librewolf in the latest release.