Although it’s not quite as good as uBlock Origin, moving to a network based setup, like PiHole or AdGuard Home, can make great strides across all your devices with minimal headache or worrying as much about Google making it harder to control your web content. It makes it very apparent when I’m browsing on my phone or iPad and they switch over to LTE because all the sudden there are ads everywhere.

At some point I’m sure they’ll start trying to bypass local DNS by forcing DNS over HTTPS to only their approved servers, at which point someone will build a MITM HTTPS proxy for home users that you can seamlessly install onto a Raspberry Pi until we see the next escalation in the never ending battle for our eyeballs.

GP here. You can also try NextDNS.io, which allows you to choose blocking lists. There are apps for iOS as well as other platforms to allow it to be used on all networks (or even configure it not to be used on specific WiFi networks).

If uBlock Origin doesn't update, there'll be a dozen adblockers that work with Manifest v3 on day 1.

It should be quite trivial to write an adblocker that integrates with EasyList using the new APIs.

> If uBlock Origin doesn't update, there'll be a dozen adblockers that work with Manifest v3 on day 1.

You seem to not know what manifest v3 is actually doing.

Any adblocker with a static list of domains per-update of the crx file's manifest is useless. Users would have to install hundreds of extensions (each with dozens of domains that they themselves block), just to have the same functionality.

If any anti adblocking team of any ad network decides to just rename foo.tracker.net to bar.tracker.net, all adblocker extension users would have to REINSTALL the chrome extension manually because the manifest's list of domain is statically builtin.

You're operating off of outdated information. Rules do not need to be baked into the manifest.

>The Declarative Net Request API now allows for the registration and removal of dynamic rules - specified at runtime rather than statically in the manifest. We’ve also added the capability to remove common tracking headers, such as Referer, Cookie, and Set-Cookie.

https://blog.chromium.org/2019/06/web-request-and-declarativ...

If its trivial what's stopping you from doing it?

Why would I need to? Manifest v3 isn't even out yet, and dedicated developers will easily beat me to the punch.

What? Manefist v3 is not even out yet...

oof, really hope this doesn't see the light.

On the other hand, this might be the push some people need to start using Firefox.

Or, ironically, MS's chromium fork powering Edge

> MS's chromium fork powering Edge

Microsoft will simply follow Google's lead.