Most people still haven’t heard of Manifest V3, so if you are one of those not using Firefox, this is for you.


If you’ve been on YouTube or Reddit August last year, you might’ve seen this screen yourself, or a screenshot of someone else getting it. This of course, I am talking about the infamous YouTube ad blocker blocker popup, discussion exploded on Reddit mostly consisting of people complaining about ads, as well as an angry mob storming r/memes, turning it into a Firefox propaganda centre.

About a month later, different adblockrs eventually found their way of bypassing detection, and they work on YouTube again. So natrually Redditors thought they’ve won another war against big tech, completely ignoring Google’s original plan to kill off adblockers by June this year.

So all extensions, including adblockers follows a specification called the Manifest V2. The Manifest allows extensions to do certain things, say accessing browser tabs or to change browser settings. All while putting some limitations, and prevent extensions from doing crazy stuff like installing a virus to your system. But too much limitation, is what pisses off many extension developers about the upcoming ManifestV3.

In this article written by the EFF, they interviewed developers responsible for popular extensions, where most described ManifestV3 as a downgrade, with some accused it for being purposefully bad. I particularly like this one from the creator of SingleFile, “I consider the migration to Manifest V3 to be a major regression from a functional and technical point of view.”

After an update in June this year, a feature called the WebRequest API will be removed, and the adblockers and tracker blockers that depend on this feature will stop working. Since the business model of Google is to track your online activity and then show you personalised ads, it is not difficult to see why this feature is removed.

Not only are they sacrifising user experience for monetary gain, they are forcing the same update on all Chromium browsers as well. I am hereby devastated to inform you that this is not the first time they have done it, and it will not be the last time they will do it.

But there are also good news, non-Chromium browsers will not be affected by the Manifest V3, and if you are already using one, you will be exempt from any future nonsense Google throws in your way. So if you are considering switching to one, unless Safari is your goto browser, which lacks competent extensions support, you can still get your adblockers, another adblockers, all the adblockers.

So are you going to make the switch before the update? Let me know in the comments down below, anyways I will be seeing you in two weeks, have a good one.


An article for more my ranting needs https://gmtex.siri.sh/fs/1/School/Y12/Cssoc/chromium.html

  • UltraMagnus0001@lemmy.world
    link
    fedilink
    arrow-up
    36
    ·
    7 months ago

    I’m gonna be cocky and sit on my high horse to say I switched back to Firefox many years ago when they got rid of the memory leaks

    • gjoel@programming.dev
      link
      fedilink
      arrow-up
      24
      arrow-down
      2
      ·
      7 months ago

      Firefox - Accidentally introduces memory leaks. People flee in droves.

      Chrome - Intentionally introduces privacy leaks. People go “eh” end keep using it.

      Gotta protect that memory!

    • RippleEffect@lemm.ee
      link
      fedilink
      English
      arrow-up
      12
      ·
      7 months ago

      Yeah Firefox definitely had issues but right now I think it’s the best browser available.

    • odelik@lemmy.today
      link
      fedilink
      arrow-up
      8
      ·
      7 months ago

      I switched off of Firefox because of those memory leaks. I remeber when it hit the tech news circles when the community contributer that was frustrated with them went in and fixed two of the biggest culprits.

      Then I just didn’t bother til somewhat recently. For the most part, it’s great and does what ilI want/need. Biggest complaint is that some UX overhauls are needed for Mobile FX, especially around tab management.

    • banazir@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      The last time I remember Firefox having serious memory leaks they called it Firebird. Guess I’ve been lucky. Or in a comfortable ignorant haze.

      • odelik@lemmy.today
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        7 months ago

        Firefox had some major memory leaks when Chrome first launched (2008). It became noticeable with the more tabs you had and the longer the browser was opened. This was also during the days for consumer systems with 16GB max RAM & 32GB on higher end enthusiast systems.

        We also have to remeber that this was 10 years before Google removed their “Don’t be Evil” motto, and there was still a great deal of trust that had been earned by tech professionals.

        So when Chrome came in, had a minimalist UI (for the time) and was light weight and memory light without any obvious memory leaks, it was a performance boost for a toooon of users.

        Chrome has since become a memory hog and is now being developed and pushed by a company that has become heavily enshittified & evil. Firefox has become lightweight, memory efficient, and is an FOSS product that’s not evil and enshittified making it the right choice in 2024, but is going to be an uphill battle that hopefully more tech professionals move to as Manifest V3 becomes a reality.

      • nix
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        It had a leak a few years back. Not a huge one, but it’d add up on devices that had a ton of tabs or were always on.