• mtchristo@lemm.ee
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    1 year ago

    They have been postponing it for a long time now. But uBlock origin has a light version they expect to work with V3. I wonder why they bother in the first place when they can just focus on Firefox

    • ReversalHatchery@beehaw.org
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      But uBlock origin has a light version they expect to work with V3

      It just “kinda” works. It cannot nearly load all the network filters that it would normally use.

        • Madis@lemm.ee
          link
          fedilink
          arrow-up
          10
          ·
          1 year ago

          Yes, it blocks ads, and likely the YouTube ones too. The current problem with YouTube is just their anti-adblocker which needs very frequent filter updates and unlike MV2, filter updates in MV3 need the update of the entire extension (think approval periods etc).

          • ExLisper@linux.community
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            5
            ·
            1 year ago

            That was my understanding. People talk about this change like it’s going to disable adblock extensions completely which is clearly not the case. So far no one really explained what the actual impact will be. Do you know that? I see youtube ads might be harder to block. Anything else?

            • mihor@lemmy.ml
              link
              fedilink
              arrow-up
              8
              arrow-down
              1
              ·
              1 year ago

              Yeah, I would like to know that as well.

              Although if updating the adblocker’s list is not instant, as with wm2, it is basically a losing race with Google, since they can change the ad domains even before the adblocker update is applied.

              • Saik0@lemmy.saik0.com
                link
                fedilink
                English
                arrow-up
                2
                ·
                1 year ago

                Or worse, since the adblocker no longer has direct access, they can just set chrome to ignore it’s requests/changes when it benefits them.

            • ReversalHatchery@beehaw.org
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              Oh fear not, limiting filter list updates to addon updates is a huge problem. For those users who rarely restart their browsers it’s even bigger of a problem: updating the addon (for the up to date filter lists) also means that all of the already loaded websites will lose the filters until you reload them, which is both not obvious to be needed and very painful, when you are using your browser for other things than consuming.

              Also, does that also mean that custom filter lists are impossible anymore?

              Besides these, also take into account that approval of addon updates can take a long time, quite often days, while the filters need to be updated more often (once or twice a day) for websites to not break for the majority of the users.

              Yes, thinking about it, I still confidently think that chrome’s changes are unacceptable and are dealbreakers, and google is very clearly trying to curb content blockers with whatever tools available. Fortunately I don’t have to use that garbage anywhere.

        • ReversalHatchery@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Not really. In some cases it is able to, but as I said, ublock cannot load it’s filters, and so it can filter out much less things. Don’t forget that ublock does not only block ads, but disruptive popups and obsessive data mining too. With this change of chrome, it is simply unable to do that reliably.

    • Madis@lemm.ee
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Well, Firefox also plans to deprecate MV2 at some point (deadline to be announced at the end of this year), the difference is just that their implementation of MV3 is more flexible at the points Chrome was criticized for.