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

  • schema@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    8 months ago

    I tried revanced for a while. It worked for a little and one day videos were suddenly buffering for 5 minutes at a time after around a minute of playing. I read online that it might have been yt measures against using a client like this (changing account or logging out didnt do anything. Browser played the videos fine)

    Firefox with adblocker and the extension to be able to play in the background has been my savior. Works flawlessly.

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

      Every other month, YT update something that break Revanced.

      So I just went to the Revanced app to see what’s the newest recommended version of YT to download and patch. Then a quick reinstall and everything is back to normal. Don’t even have to re-login.

      Been doing that for over a year. Imo, the native app’s experience is always a thousand times better than the mobile web browser.

    • PhAzE@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      It was, and it was after 30 seconds. You install the updated revanced, and turn on app version spoofing in the settings and no more buffer issue.