If you have uBlock Origin, you might notice Chrome automatically disabling the extension.

Google Chrome has begun to phase out uBlock Origin. The developer of the free ad blocker, Raymond Hill, recently reposted a screenshot that shows Chrome automatically turning off uBlock Origin because it is “no longer supported.”

The change comes as Google Chrome migrates to Manifest V3, a new extension specification that could impact the effectiveness of some ad blockers. uBlock Origin has launched uBlock Origin Lite, which uses Manifest V3, in response to the transition. However, you have to manually install the extension because it’s “too different from uBO to be an automatic replacement,” according to a FAQ Hill that posted to GitHub.

  • fine_sandy_bottom@lemmy.federate.cc
    26·
    1 month ago

    I’ve been a firefox supporter since netscape.

    That said, things aren’t going great.

    Because it’s market share is in the toilet more and more web sites just aren’t supporting it any more. My university’s website, some government websites, and 2x industry platforms I use for work just plain do not work in firefox.

    Mozilla just bought an advertising company. They can spin it as they like but basically, mozilla’s primary revenue source in the future is going to be ads.

    They just had a throw down with the developer of uBlock. I don’t think this is particularly meaningful, but it’s not a tick in the right column.

    • thatsnothowyoudoit@lemmy.ca
      6·
      30 days ago

      Nothing a user agent spoofing extension can’t fix.

      Also, if anyone has concerns about Firefox there are some really interesting forks.

      Zen has been my go to for a couple of weeks.

      • el_abuelo@programming.dev
        21·
        30 days ago

        Why is that? Folks aren’t going round writing user agent parsers to maliciously disable functionality in Firefox. They’re just writing bad code that doesn’t work on anything but the browser they use.

        I use Firefox mainly because I don’t trust Google and at work it ensured at least one of us sees bugs that chrome users don’t.

      • fine_sandy_bottom@lemmy.federate.cc
        11·
        30 days ago

        When I say “aren’t supporting” I mean “not testing”. These sites are broken.

        All Firefox forks in existence are merely soft forks. They’re not committing code, they just compile with different flags and configure.

          • fine_sandy_bottom@lemmy.federate.cc
            11·
            30 days ago

            That link is talking about tabs?

            That’s just css. Every soft fork messes with that. You can yourself in user.css

            The big deal with tabs is getting UX right. It’s more about how it looks and whether it’s intuitive, rather than implementation.