Google prepares for Chrome extension Manifest V2 phase out
www.theregister.com
Starting Monday, users will gradually be warned the end is near

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.

      • bobs_monkey@lemm.eeEnglish
        10·
        7 months ago

        It just has a crap load of software packages it depends on to work properly (though a number of them seem like fonts). I have reasonably fast computer, and it’s been compiling for about 45 minutes at this point.

        • TachyonTele@lemm.eeEnglish
          2·
          7 months ago

          Ah compile… guess I’ll stick with regular Firefox. There are some magiks I don’t tamper with.

          • grue@lemmy.worldEnglish
            2·
            7 months ago

            I mean, if you’re intimidated by compiling you probably shouldn’t be using Arch to begin with.

            (I’m hoping that you didn’t understand the “on AUR” part of the comment as well as the “dependencies” part, and actually use a more reasonable distro that isn’t subject to the issue @bobs_monkey is complaining about.)

              • grue@lemmy.worldEnglish
                3·
                7 months ago

                • Arch is a Linux distribution that intentionally requires a bunch of relatively-complicated manual steps to install, so “I use Arch BTW” has become a meme among people who want to brag about how ‘l33t’ they are.

                • AUR is Arch’s package manager.

                • A package manager is a software database that lets you easily install apps with a single command (e.g. [tool-name] install [app-name]) along with all the software libraries they depend on (i.e. their ‘dependencies’), such that you only need one copy of each library no matter how many apps use it.

                (Without a package manager, there are two other ways installing apps can work: either an app can come with its own copy of all its dependencies, which means it takes up a lot of disk space unnecessarily, or the user can be responsible for installing all the dependencies separately, which is a gigantic pain in the ass. Windows takes the former approach, while Linux, before package managers were invented, tended to do the latter because open-source software was distributed mostly as source code you had to compile and link yourself.)