And by requiring an Apple Developer Account and associated tooling, they've made them just hard enough to develop that the long tail won't bother porting.
Network-level blockers are very crude and tend to cause errors that are hard to debug and fix. I get it if you have no other option and they work well enough with a very conservative blocklist, but in my experience a dedicated extension will block more ads, block them better (no blank spots in pages), break legitimate content less often and when it does be far easier to temporarily bypass.
Sure but the point is a browser level adblockers can separate the tracker content from the legitimate content while a network level blocker can either block both or neither.
So many large sites have started serving ads through the hostnames that serve their applications. It feels like a losing battle to keep only blocking at the DNS level.
Unless you’re also automating a VPN connection to your home network when you leave it, which can be very helpful if you’re running something like pihole
I'm on Safari, with the occasional testing and account segregations with Chrome. The combination of AdGuard[1] (found via SetApp[2]) and NextDNS[3] works for me well on Safari.
I use the AdGuard extension too, with a Raspberry Pi running AdGuard Home which in turn uses NextDNS. I highly recommend every part of this setup, it's maintenance free, extremely reliable and I can't remember the last time an ad or tracker got through it.
The adblocker Wipr has recently added something beyond the Content Blocker API with Wipr Extra. I only found it because I had forgotten to switch to AdGuard on my office Mac, and Wipr Extra showed up in an update. Lots of restrictions and caveats though about what it can and can't do. Some details at