The new MV3 architecture reflects Google’s avowed desire to make browser extensions more performant, private, and secure. But the internet giant’s attempt to do so has been bitterly contested by makers of privacy-protecting and content-blocking extensions, who have argued that the Chocolate Factory’s new software architecture will lead to less effective privacy and content-filtering extensions.
For users of uBlock Origin, which runs on Manifest V2, “options” means using the less capable uBlock Origin Lite, which supports Manifest V3.
Manifest v3 has an upper limit of rules that can be implemented, so if you don’t see how supporting it is a problem, you’re blind.
Supporting v3 and v2 inevitably leads to v2 support being dropped. Firefox has done this plenty in the past with the goal of “cleaning up the code base”. Taking care of 1 code path > Taking care of 2 code paths.
It’s simple on the face of it, and all results in less control for web users.
Firefox’s implementation of manifest v3 is a bit different than Chrome’s, and still allows for blocking webrequests with no upper limit.
https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/
https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/
I for one welcome Mozilla’s use of embrace, extend, exterminate.
deleted by creator