5 ms·
Yet another reason to use Pi-hole. The web browser is the wrong place to try and fight against this sort of thing. Secure your home network once instead of figh
by dahfizz 5y ago
Yet another reason to use Pi-hole. The web browser is the wrong place to try and fight against this sort of thing. Secure your home network once instead of fighting an arms race on each device you have.
- kaba0 5y agoHow does it help here? They can trivially include ads server-side, pi-hole would see nothing at all.
- guntars 5y agoYou can do it, but it’s not done commonly. The most common way ads get onto the page is by including a third party script which is easily blocked.
- irrational 5y agoToday, but this entire discussion is about how things will work tomorrow.
- dahfizz 5y agoIt would be easy to implement server-side rendering, but it carries significant cost in processing time and networking. If they can block all adblocking browser extensions by abusing WASM, the cost of server-side rendering will outweigh the 0.0001% of people that have a pihole set up.
- duxup 5y agoCan you target "opaque binary blobs of code" with a pie-hole?
- EvanAnderson 5y agoDNS over HTTPS and, eventually, certificate pinning in the WASM-based DoH client running inside your browser will render your Pi Hole useless. It'll all just be opaque TLS to your network gear. Network operators who legitimately need to control traffic on their networks are lumped in with human rights-violating nation states. That includes you on your network.
- dahfizz 5y agoCan you substantiate any of that? DoH is a feature of the browser that can be configured or disabled. Firefox even disabled DoH automatically if it detects you are using a custom DNS server which blocks "potentially malicious content"[1]. [1] https://support.mozilla.org/en-US/kb/firefox-dns-over-https https://support.mozilla.org/en-US/kb/firefox-dns-over-https
- EvanAnderson 5y agoI'm not talking about the browser doing the name resolution. I'm talking about the opaque binary running inside the browser doing name resolution (either by way of DoH with a pinned certificate, or a custom name resolution protocol running over TLS). You won't get a say in what that opaque binary does (w/o modifying it). Is anybody doing this now? I doubt it. Will somebody do it? Yeah. Definitely. When the "browser" is an embedded device (like Google Chromecast devices hard-coded to use 8.8.8.8 for DNS) you'll have no configurability there either.
- newscracker 5y agoThere’s a place for DNS based ad blocking like Pi-hole or NextDNS and a place for first party ad blocking and element blocking (and even script blocking) using uBlock Origin, NoScript, etc. They’re complementary in certain ways.
- deleted 5y ago[deleted]
- asciimov 5y agoPi-hole wont protect you here, they will send the entire page, ads and all as an encrypted binary blob. Decrypting it is illegal, and since the data is coming from a single source Pi-hole can't block it. Pi-hole (and ad-blocking) days are numbered. Hopefully that day is further out than I dread.
- bruce343434 5y agoDecryption is illegal? Lol what?
- adkadskhj 5y agoI think they're implying DRM laws associated with the data-streaming.
- bruce343434 5y agoI have faith that that's only a matter of time before somebody makes a patch that just does the decryption without fuss.
- bozzcl 5y agoWait, how is decrypting the WASM blob illegal?
- deleted 5y ago[deleted]
- AshamedCaptain 5y agoA proxy can do very little to actually block ads compared to what a web browser can do. Web browser _is_ the right place, or at least it is the only place where you can actually do something intelligent to block ads. For example, if you are blocking ads at a proxy, it is trivial for site owners to detect it and then your filtering proxy can literally do nothing to compensate. A huge chunk of all the filters in adblocking lists are basically to defeat anti-adblocking functionality...