We’ve been anticipating it for years, and it’s finally happening. Google is finally killing uBlock Origin – with a note on their web store stating that the extension will soon no longer be available because it “doesn’t follow the best practices for Chrome extensions”.

Now that it is finally happening, many seem to be oddly resigned to the idea that Google is taking away the best and most powerful ad content blocker available on any web browser today, with one article recommending people set up a DNS based content blocker on their network 😒 – instead of more obvious solutions.

I may not have blogged about this but I recently read an article from 1999 about why Gopher lost out to the Web, where Christopher Lee discusses the importance of the then-novel term “mind share” and how it played an important part in dictating why the web won out. In my last post, I touched on the importance of good information to democracies – the same applies to markets (including the browser market) – and it seems to me that we aren’t getting good information about this topic.

This post is me trying to give you that information, to help increase the mind share of an actual alternative. Enjoy!

  • cum@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    13
    ·
    1 month ago

    What you’re talking about is webcompat and is a very complicated issue. Also I’ve talked to some Mozilla devs who gave me multiple examples of Chromium rendering something wrong, and they’d have to intentionally break Firefox to render it incorrectly too, just so the end user would get a more consistent experience. Of course these issues happen more and more when things are only tested for one browser.

    • Yi K@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 month ago

      This is Chromium monopoly. At this time instead of W3C standards, Chromium itself becomes the standard.

    • ElectricMachman@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 month ago

      Maybe there could be some sort of compatibility flag in Firefox which detects non-standard pages designed for Chrome. We could call it… hmm… something like Quirks Mode?