You just can’t do it before the request hits the browser, so you can’t pretend to be a vpn inside the browser.
Blocking or redirecting all requests, based on dynamic values, adapting all headers through webrequest and not showing any ads and removing them from the page is still possible with service workers and content scripts.
The only issue is with regards to “static” rules and modifying them before they hit the browser. After that you can still do everything you could before. The only issue is bandwidth, but this should always have been an app to intercept all network requests instead of something inside the browser (like a vpn adblocker)
It’s technically possible to bifurcate an adblocker like that but it’s an ugly setup and you would only do it if a gun was held to your head by an ad monopoly.
That said, it may be a good idea in the current situation.
^ This is really stretching the meaning of ‘VPN’!
The only two things you cannot do is declare them as static rules (well you can but not unlimited), and look and modify every header before it hits the browser.
And yes, you could have an app with a browser extension like Adblock already did for years without issues.
You could also have only a browser extension and have all the user functionality you have now, the only difference being it just slightly slower, and you still having the network load the ads (but not the page you’re on).
A bit annoying? Sure. But it’s hardly the severe problem it’s being made out to be.
It's not just bandwidth, though. It's also about not allowing ad companies to collect data about you such as which sites you view.
Not showing ads is important, but it's only half the battle.
Which is a lot.
And even if you somehow hit this number, afterwards you can still intercept every request before the user sees it to modify headers or remove ad content.
Is it annoying? Sure. But again, you can technically still do everything you could before.
not if DNS is hosted on the same servers as eg google search itself. then they would have to block google search in order to block DNS.
Such devices have a pretty simple architecture: the highly performant data plane where DPI is implemented in the hardware (using either ASIC's or FPGA's – don't have enough information), and the control plane. The control plane comes with a SDK of sorts that DPI appliance users can use to tailor the appliance to their environment and that is used to «refine» the data plane behaviour, i.e. sending down / updating DPI pattern matching / processing rules.
I think the weak points are wholly untechnical e.g. Google would often give in to protect the $$$ they make in a region.
Unencrypted DNS also has to be bootstrapped by a well-known set of IPs. None of the current DNS propagation system would work if it wasn't for the hardcoded IPs for the root DNS servers at *.root-servers.net.
And, of course, end-user devices still need an IP to query for DNS, it's just that it's almost always supplied automatically via DHCP or similar.
A caveat of encrypted DNS is that it has to be bootstrapped via traditional, unencrypted DNS or via a well-known set of IPs. Currently, most clients using DoH/DoT use one of a small handful of providers. Cloudflare, Google, Quad9, etc. A motivated government could block those endpoints pretty easily.
Of course, a client using encrypted DNS could just refuse to work when encryption is blocked, rather than falling back to traditional DNS. But that could mean the client is unusable in the country implementing the block.
This sort of reminds me of when Kazakhstan announced they were going to MITM all TLS sessions within the country, and all citizens would need to manually install a root cert. Google, Apple, and Mozilla chose to completely block their root cert, so it would be unusable even if users chose to go along with it. https://en.wikipedia.org/wiki/Kazakhstan_man-in-the-middle_a... Seems like the browser devs won that political standoff, but would they fight the same battle if DoH/DoT was blocked?