Google is Killing uBlock Origin. No Chromium Browser is Safe.
www.quippd.com
We’ve been anticipating it for years,1 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”.2 Daly Barnett. “Chrome Users Beware: Manifest V3 is Deceitful and Threatening.” EFF, December 9, 2021. ↩ Lawrence Abrams. “Google warns uBlock Origin and other extensions may be disabled soon.” Bleeping Computer, October 13, 2024. ↩

Google is weakening ad blockers as part of their MV3 extension standard and this will trickle down into all Chromium browsers. Built in ad blockers lack features compared to uBlock Origin as well.

  • yoasif@fedia.ioOP
    1·
    16 days ago

    You have to remember that sometimes when that shiny new CSS feature comes out, it is underspecced, with unhandled corner cases – “just do what Chromium does” is not a standard – or is it? Having multiple implementations of a spec prove that it is interoperable - without that, you might have a good spec, or you might have a spec that says “whatever Chrome does is what is expected”. Not sure that is what we want from new CSS (or any) features.

    • jeremyparker@programming.dev
      1·
      10 days ago

      You make a compelling point, for sure. There are definitely features that fall into that category (eg page transitions), there are a lot of other things coming out these days that just make life easier.

      For example, in chrome (and in the spec) you can now animate between ‘height: [number]’ and ‘height:auto;’ just the other day, I had to write a python function to estimate the highest of a menu based on its length * the line height of the list items, so I could provide an exact height to animate to. It works, but it’s hacky and gross. It would be nice to have access to the solution.