I think we're there, not 2 years away.

I have software that won't work quite right in Safari or Firefox through a VPN every single day. Maybe it's the VPN and maybe it's the browser but it doesn't matter. We're at IE levels it's just ever so slightly more subtle this time. I'm still using alternatives but it's a battle.

VPN's layer 2... I suppose it could be resizing packets in such as way as to make it glitch out, but that just seems improbable.

Some of the warez sites I download torrents from have captchas and other javascripticles that only work on Chrome, but I've yet to see it with mainstream sites.

Fight the good fight.

The VPN could be on an IP address with a bad reputation that's getting soft-blocked by some stuff

> I can't use adblockers on Chrome

Why does this myth persist?

uBlock Origin Lite works perfectly fine on Chrome, with the new Manifest v3. Blocks basically all the ads uBlock Origin did previously, including YouTube. But it uses less resources so pages load even faster.

There's an argument that adblocking could theoretically become less effective in the future but we haven't seen any evidence of that yet.

So you can very much use adblockers on Chrome.

If uBO Lite is really better, why does uBO exist?

Because uBO Lite uses a newer Chrome function call (declarativeNetRequest) that didn't exist previously (original uBO was based on webRequest).

webRequest is slower because it has to evaluate JavaScript for each request (as well as the overhead of interprocess communication), instead of the blocking being done by compiled C++ code in the same process like declarativeNetRequest does.

uBO also has a bunch of extra features like zapping that the creator explicitly chose not to include in uBO Lite, in the interests of making the Lite version as fast and resource-light as possible. For zapping, there are other extensions you can install instead if you need that.

They're two different products with two different philosophies based on two different underlying architectures. The older architecture has now gone away in Chrome, but the new one supports uBlock Origin Lite great.

Thanks, I'll try it out then.

I think you're overstating it a bit. There were definitely features that couldn't be implemented due to MV3 limitations rather than because the developer chose to leave them out.

https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

Hm, I can't tell how serious these limitations are, but there are a lot, and this one stands out:

  replace=, can't modify the response body (full support is only possible with Firefox MV2)