The issue with deeper and deeper ad blocking technology is that you're going to end up putting more and more trust into your ad blocker.
uBlock Origin requires access to the DOM, where it can do nasty things like overwrite window.fetch or window.XmlHttpRequest and intercept network traffic. PiHole, just based on the way it operates, has to route all your network traffic along a different route, and it's up to you to watch its upstream output to make sure it's not doing something bad.
I think there's some benefit to the way Apple is intentionally limiting the available surface for content blockers, but it'd be nice to expand on that surface in limited means (eg: freeze library functions so more of the DOM can be accessed, but at the risk of breaking badly-behaved websites) or at least to get a better, plain-English explanation as to _why_ those decisions are being made.
> The issue with deeper and deeper ad blocking technology is that you're going to end up putting more and more trust into your ad blocker.
To be honest, I trust my ad blocker more than I trust Apple.
This is not a joke. Remember that Apple takes literally billions of dollars per year in payoff to make Google the default search engine in Safari. Apple's interests are not exactly aligned with mine.
uBlock Origin requires access to the DOM, where it can do nasty things like overwrite window.fetch or window.XmlHttpRequest and intercept network traffic. PiHole, just based on the way it operates, has to route all your network traffic along a different route, and it's up to you to watch its upstream output to make sure it's not doing something bad.
I think there's some benefit to the way Apple is intentionally limiting the available surface for content blockers, but it'd be nice to expand on that surface in limited means (eg: freeze library functions so more of the DOM can be accessed, but at the risk of breaking badly-behaved websites) or at least to get a better, plain-English explanation as to _why_ those decisions are being made.