Starting June 2024, adblockers such as uBlock Origin and many other extensions on Chrome will no longer work as intended. Google Chrome will begin disabling extensions based on an older extension platform, called Manifest V2, as it moves to the more limited V3 version.

    • JohnEdwa@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      Just like they keep insisting we disable adblockers to view them. Both are easy to circumvent, but mostly my reaction is to just close the tab and look for the content elsewhere.

      • pulaskiwasright@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Google has already talked about a plan to cryptographically authenticate a browser. We likely won’t be able to get around that.

        • online@lemmy.ml
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          Creators really need to release torrents of their libraries of content so that we can access it without having to go through platforms. Maybe release them twice a year? Four times a year? Imagine just pulling up a creator’s torrent, clicking which videos you want to download to watch, then waiting a few minutes and playing it right off of your computer. I bet that could also work with peertube?

    • atrielienz@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      There’s literally a work around for Google making YouTube videos pose pause for 5 seconds before playing on Firefox due to adblocker use. It’s to use the adblocker to trick Google into thinking Firefox is chrome.

      • pulaskiwasright@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 year ago

        They are also working on ways to let websites cryptographically authenticate a browser. So if they wanted to badly enough, that workaround wouldn’t work.

        • atrielienz@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I don’t necessarily agree. I see what you’re saying but they’ve been losing this pretty much at every turn.

          • pulaskiwasright@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            They haven’t really tried because of anti trust. They need buy in from other major players and then they will be successful.

    • GigglyBobble@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Implicitly they often do already because web devs have become more and more lazy and don’t test any browser but the one they prefer themselves.

      • pulaskiwasright@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Google has already talked about a plan to cryptographically authenticate a browser. We likely won’t be able to get around that.

        • GigglyBobble@kbin.social
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          As far as I remember they acted in parallel and pushed the implementation already. They claimed it to be rogue actions of over-enthusiastic devs after the concept paper caused a public outcry.

          I haven’t followed that issue but Google will continue to try to close us in, for sure.