For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.
What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.
Has anyone notice safari letting youtube ads through on iOS recently? (I also use AdGuard DNS on my phone, so I guess that’s stopped working too)
I mean I just used a sideloaded yt mod but then i kinda got too excited with exploits and broke the phone and had to update it and now I’m on grapheneOS lol. Oh besides, I just used it mostly for downloading videos cuz I don’t really like google. (Ironic to buy a google phone to degoogle it.)
I’d love to try graphene. Unfortunately, I bought an iPhone this year, so now I feel obligated to use it until it breaks. Thanks for being the guinea pig for me to start with a better experience when my time comes o7
My AdGuard is working well against YouTube, and I back it up with PiHole as well
The ad games is always one of whack-a-mole; companies like Google have it in their best interest to find ways to get around ad blockers. The ad block developers then find newer ways to block ads, and the cycle continues.
a DNS AdBlocker just stop a request to a specific domain. If youtube serves video and ads from the same server you do not know which one is an ads and which one is a video on the DNS level. Furthermore you have some devices hardcoding DNS server (google homes are common for calling google DNS directly instead of getting the DNS from the Router) which makes it very hard to use DNS level AdBlockers.
Google spends a lot of money mixing ads and legit content to make it impossible to block, it is not safari “letting ads through” is more like safari cannot identify ads anymore.
Ohh, cool that makes more sense. Thanks for the info. Eventually I’m gonna get PiHole set up, but I guess that would face the same issue… yt-dlp might be the best way
Correct, pihole alone cannot fix it. You can fix the issue of hardcoded DNS with a firewall translating requests to DNS into another DNS, but that also has issue with DNS over https. The only reliable way I saw for YouTube Ad block is either custom apps or browser level Adblock like Brave Shield (which Firefox is also integrating as it is open source)
That info was very valuable for me, thanks! I’ll save this comment.
Just so you know, AdGuard Home exists, that is more or less the same as PiHole but uses less resources. I run it on my router (and I use the router firewall directly to force the DNS to AdGuard) with SSL certificates automatic renewal with certbot so that encryption is supported. I think you can ask an AI for help on your specific setup.