• Railcar8095@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      6 months ago

      I guess extension developers will slowly stop, unless extremely hampered.

      Will there be many extensions with active development that still use V2? Either they focus on Firefox or they have two versions.

      At that point, why not make ublock part of Firefox, like brave did?

        • Railcar8095@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          6 months ago

          It’s more work and will create different set of features.

          So no, not crazy, but really inconvenient and for a very limited amount of users

      • jennraeross@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        6 months ago

        I think Firefox will support both v2 and v3 extensions, so devs can use whichever makes more sense for their project. It has been a while since I looked into it though.

        • Railcar8095@lemm.ee
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          1
          ·
          6 months ago

          For the time being, yes, they will support both. But V2 will only work on Firefox (and forks) and I think brave, a very small percentage of users.

          So given that it will be like supporting two different extensions, I assume most extension developers will just switch to v3.

          How long after most extensions are v3 until Firefox drops/stops supporting is anybodies guess.

          It’s actually a great example of how chromes dominant position is screwing other browsers

  • umbrella@lemmy.ml
    link
    fedilink
    English
    arrow-up
    37
    ·
    6 months ago

    time to treat that firefox allergy of yall if ya want to keep adblocking.

    • Gork@lemm.ee
      link
      fedilink
      English
      arrow-up
      13
      ·
      6 months ago

      But Google search has gotten so much more interesting these days. Glue in pizza, spaghetti in gasoline sauce, jumping off bridges when feeling depressed.

      • Railcar8095@lemm.ee
        link
        fedilink
        English
        arrow-up
        7
        ·
        6 months ago

        To be honest, jumping off a bridge stops feeling depression… And so the other feelings.

        But for real, I hope nobody did anything irreversible due to this stun.

    • GreyBeard@lemmy.one
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 months ago

      Unfortunately, in mobile phones, there is little choice. It is almost 100% Android or iOS. Even a lot of “flip” phones are now Android. I’d love to have a KDE based phone, but the options are slim, and the functionality is missing.

      • rigamarole@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        6 months ago

        Ironically, the Google Pixel with GrapheneOS is a very privacy-focused option with no bloatware.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    4
    ·
    6 months ago

    This is the best summary I could come up with:


    "Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension.

    The most salient of these is the blocking version of the webRequest API, which is used to intercept and alter network traffic prior to display.

    Under Manifest V2, it’s what extension developers use to stop adverts, trackers, and other content appearing on pages, and prevent certain scripts from running.

    The new MV3 architecture reflects Google’s avowed desire to make browser extensions more performant, private, and secure.

    Li acknowledged the issue by noting the ways in which Google has been responsive, by adding support for user scripts, for offscreen documents that have access to the DOM API, and by increasing the number of rulesets in the declarativeNetRequest API (the replacement for webRequest) to 330,000 static rules and 30,000 dynamics ones.

    And by the beginning of 2025, when the API changes have been available for some time in the Chrome Stable channel, Manifest V2 extensions will stop working.


    The original article contains 585 words, the summary contains 167 words. Saved 71%. I’m a bot and I’m open source!

  • Septian@lemmy.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    So, I keep meaning to look into this but I come from the wrong background to have an intuitive grasp of the pieces at play here. My work is primarily in back end systems development for data driven models and I have very little understanding of how networking elements interact or even what they are, for the most part. If someone with that background is reading these comments and willing to take the time, would you be able to provide an explanation for the differences between Manifest V2/V3 and how V3 prevents ad blockers from working?

    • Madis@lemm.ee
      link
      fedilink
      English
      arrow-up
      12
      ·
      edit-2
      6 months ago

      With manifest v2, extensions could block the content however they wanted, reading and modifying DOM as they see fit.

      Google claims that it is a security risk, so with manifest v3, extensions can only create and give the browser rules and the browser itself will block content based on them. The rules have a limit in size and capabilities.

      If that was still not clear, try thinking of unrestricted SQL access vs a UI for modifying a database.

    • AProfessional@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      6 months ago

      The webRequest API allowed intercepting any network request in v2. Firefox also has an api for dns resolving. Lastly chrome now has a limited size for content blocking rules. All adding up to more limited blocking.