Was casually reading through Firefox release notes for version 115, and in “Changes” section there is an introduction of a new back-end feature that restricts extensions behavior
We have introduced a new back-end feature to only allow some extensions monitored by Mozilla to run on specific websites for various reasons, including security concerns.
This feature is obviously still under development, but it already forced people to look for fixes. This suggests the user-unfriendliness of this feature, which may be related to the goals that the infamous Web Integrity API is seeking: partly, controlling and limiting extensions, which are there for the community(!)
I, of course, understand that this update dates back to 4th of July 2023 - some time before this DRM-the-web thing exploded, but still it contradicts things that Mozilla stated in opposition of Google’s plan to hijack [even more] the internet.
How long before the YouTube page will be too private, sensitive and important to allow uBlock Origin from running on it? Will Mozilla decide that youtube.com is “quarantined domain” or will it accept suggestions from its monopoly colleagues?
This feature bug can be fixed by going to about:config and setting “extensions.quarantinedDomains.enabled” to “False”. For now.
Not trying to make a fuss and/or cause a hysteria, just pointing out that such a thing was introduced and slipped under the radar (haven’t seen a discussion about this on the internet). Mozilla may have other intentions for it, but it doesn’t look like something made truly “for the people, not for profit” as some of Mozilla’s slogans state.
Will be happy to discuss.
EDIT: “uBlock” > “uBlock Origin”
It sounds like a decent feature if used to protect things like banking sites from potentially invasive extensions. I disable my adblocker (only extension I use) for all those types of sites.
Yes. It makes sense to limit everything except thing required to interact with such sites when accessing them, but, as history tells us, not everything served as higher purpose will remain noble and harmless. It definitely has potential to be used against users in the future. Will it? It is very much in line with what Web Integrity API proposed as a “solution”.
EDIT: added the last sentence.