Old Manifest V2 Chrome extensions will be disabled in 2024

>With Manifest V3, Google wants to make extensions safer by prioritizing privacy, but was initially criticized for the impact to ad blockers. The Chrome team has since added new features in response and is ready to disable old Manifest V2 extensions in 2024.

>Google will begin automatically disabling Manifest V2 extensions in Chrome Dev, Canary, and Beta as early as June 2024 (Chrome 127+). Similarly, Chrome Web Store installs will no longer be possible. Developers are encouraged to update and migrate before then.

>This will gradually roll out, with Google taking into account user feedback and data to “make sure Chrome users understand the change and what actions they can take to find alternative, up-to-date extensions.”

>This was originally schedule to take place in 2023, but Google spent this year closing the functionality gap between Manifest V2 and V3 with:

>Introducing Offscreen Documents, which provide DOM access for extensions to use in a variety of scenarios like audio playback
>Providing easier control over service worker lifetimes for extensions performing actions like receiving events over a longer period of time
>Adding a new User Scripts API, which allows userscript manager extensions to more safely allow users to run their scripts
>Improving content filtering support by providing more generous limits in the declarativeNetRequest API for static rulesets and dynamic rules

>We are committed to continuing to invest in the declarativeNetRequest API so we can support as many use cases as possible, and look forward to continuing to work with the community. In particular, we’d like to thank members of the WECG for their engagement, including AdGuard for sharing a significant amount of the data that drove this work, and all browser vendors who have all been a major part of designing this API.

https://9to5google.com/2023/11/16/chrome-extensions-disabled

  1. 3 weeks ago
    Anonymous

    What are the implications?

    • 3 weeks ago
      Anonymous

      This design change may revise OP's mother from her promiscuous behavior.

      • 3 weeks ago
        Anonymous

        Your response?

        https://i.imgur.com/CKRZ4ME.jpg

        >With Manifest V3, Google wants to make extensions safer by prioritizing privacy, but was initially criticized for the impact to ad blockers. The Chrome team has since added new features in response and is ready to disable old Manifest V2 extensions in 2024.

        >Google will begin automatically disabling Manifest V2 extensions in Chrome Dev, Canary, and Beta as early as June 2024 (Chrome 127+). Similarly, Chrome Web Store installs will no longer be possible. Developers are encouraged to update and migrate before then.

        >This will gradually roll out, with Google taking into account user feedback and data to “make sure Chrome users understand the change and what actions they can take to find alternative, up-to-date extensions.”

        >This was originally schedule to take place in 2023, but Google spent this year closing the functionality gap between Manifest V2 and V3 with:

        >Introducing Offscreen Documents, which provide DOM access for extensions to use in a variety of scenarios like audio playback
        >Providing easier control over service worker lifetimes for extensions performing actions like receiving events over a longer period of time
        >Adding a new User Scripts API, which allows userscript manager extensions to more safely allow users to run their scripts
        >Improving content filtering support by providing more generous limits in the declarativeNetRequest API for static rulesets and dynamic rules

        >We are committed to continuing to invest in the declarativeNetRequest API so we can support as many use cases as possible, and look forward to continuing to work with the community. In particular, we’d like to thank members of the WECG for their engagement, including AdGuard for sharing a significant amount of the data that drove this work, and all browser vendors who have all been a major part of designing this API.

        https://9to5google.com/2023/11/16/chrome-extensions-disabled

    • 3 weeks ago
      Anonymous

      ublock origin is kill on chromium as of June, I’m not sure about the userscript api though, whether stuff like violentmonkey will still work with the new api or if they’ll have to make new extensions to work with it. Either way, the time to fuck off to Firefox or other chromium browsers with a built in blocker is almost here

      • 3 weeks ago
        Anonymous

        ublock origin lite will be there, though

        https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh

        • 3 weeks ago
          Anonymous

          I've tried it and while it works surprisingly good for installing and forgetting, it's a shame it doesn't have the ability to just zap elements

          The main issue will be YouTube though, ublock lite can't update its filter lists outside of an extension update which means it'll be too slow to keep up with YouTube finding a new workaround, unless they give up on trying to do that

          • 3 weeks ago
            Anonymous

            Zap element functionality is for neons

          • 3 weeks ago
            Anonymous

            >it's a shame it doesn't have the ability to just zap elements
            gorhill is pretending that that and lots of other functionality is impossible even though the Adguard MV3 Experimental Blocker has it. Then again they were supposedly working closely with google so maybe gorhill just didn't know yet.

            time to switch back to Firefox

            No.

            • 3 weeks ago
              Anonymous

              His angle iirc is that its impossible without completely eliminating any of the supposed privacy benefit of mv3. Basically he would need to ask for permission to read your data on every page, which is the broadest possible permission. Hence, the only thing mv3 accomplished was to cripple filter lists.

              • 3 weeks ago
                Anonymous

                That's a nice story but uBlock already uses the broadest possible permissions allowed by Manifest V2 as well. Unadulterated concern trolling.

                Is there a chance that Brave or Edge or Opera will modify their browsers to still allow uBlock? Or do they all have alterior motives to see uBlock go away so they can bring in their own solutions?

                ulterior*
                https://news.ycombinator.com/item?id=38295472

              • 3 weeks ago
                Anonymous

                Well, yeah. Under v2 there's no other possible way. Under v3 you can sort of accomplish it, but not really. I think he's trying to protest the mv3 change or something.

                Is there a chance that Brave or Edge or Opera will modify their browsers to still allow uBlock? Or do they all have alterior motives to see uBlock go away so they can bring in their own solutions?

                Brendan eich made motions towards still supporting mv2, but pretty much admitted that he wouldn't have the resources to do it.

            • 3 weeks ago
              Anonymous

              > Then again they were supposedly working closely with google
              Why would you trust a company working with the glowies rather than gorill?

              • 3 weeks ago
                Anonymous

                They don't use the ABP acceptable ads list, and it's not like they whitelist Google Analytics or anything. You know AdGuard is where 95% of uBlock's filters are from in the first place, right?

              • 3 weeks ago
                Anonymous

                I enjoyed reading their investigative blogs back in the day. Adguard is alright.

              • 3 weeks ago
                Anonymous

                >95% of ublock filters
                try again. AdGuard filters are an option, but by default they are not enabled, and you actually have to go out of your way to use them. Easylist plus the ublock standard set make up the default enabled filters.

                I enjoyed reading their investigative blogs back in the day. Adguard is alright.

                Nice try shills. You can't tell me that their cto being quoted in Google's blogpost extolling the virtues of manifest v3 isn't some sort of glowie op.

                https://developer.chrome.com/blog/resuming-the-transition-to-mv3/
                >With Manifest V3, we've observed the immense effort that browser teams (Chrome in particular, but also other browsers) are putting into working on a unified platform, and I see how they are listening to the feedback from extension developers. As always, migrating to a new platform is a large undertaking, but we're very hopeful that the new unified platform will bring substantial benefits to the entire browser extensions ecosystem, and that ad blockers like us will be able to continue being up to the task and further improve.” - Andrey Meshkov, CTO AdGuard

              • 3 weeks ago
                Anonymous

                >rather than gorill?
                If you read the uBlock changelogs literally every new feature that's added is added to support newer adguard syntax. You have less than no idea what you're talking about.

    • 3 weeks ago
      Anonymous

      More fags making threads complaining about how they see ads on youtube and more fags responding to those threads by complaining that people are poor because the first two hours of work every month is tithed directly to Google.

  2. 3 weeks ago
    Anonymous

    https://developer.chrome.com/blog/resuming-the-transition-to-mv3 homosexual

    • 3 weeks ago
      Anonymous

      chrome is doomed

  3. 3 weeks ago
    Anonymous

    >two more weeks

  4. 3 weeks ago
    Anonymous

    Not my problem

  5. 3 weeks ago
    Anonymous

    That's nice but I'm sticking with Pale Moon and XUL extensions

  6. 3 weeks ago
    Anonymous

    I use brave and the United States postal service so this doesn't infect me.

  7. 3 weeks ago
    Anonymous

    time to switch back to Firefox

    • 3 weeks ago
      Anonymous

      >surely the primary motive of this decision isn't to disable adblockers
      >its for your privacy!
      Kek.

      >POZware

  8. 3 weeks ago
    Anonymous

    RIP uBlockO for Chrome.

  9. 3 weeks ago
    Anonymous

    Rip chrome

  10. 3 weeks ago
    Anonymous

    Is there a chance that Brave or Edge or Opera will modify their browsers to still allow uBlock? Or do they all have alterior motives to see uBlock go away so they can bring in their own solutions?

Your email address will not be published. Required fields are marked *