But Safari still supports extensions, surely? I’m using it with extensions, there are not stories I can see about them removing support, and their Développement pages are still up.
Their apis only support declarative static blocking lists. No heuristics, right click to block, IAB ad size detection, etc. Similar to what chrome plans to do with manifest v3.
Advertisers are already figuring out how to get around that. CNAME cloacking, proxying with same domain, etc.
Privacy is half the point of an ad blocker. I don’t think it’s ridiculous to enforce privacy constraints on something that ostensibly protects your privacy.
More specifically, they blocked extensions that work a certain way. The deal breaker for me was when uBlock origin was no longer able to run. I immediately switched to Firefox and Brave.
In July 2018, uBlock.org was acquired by AdBlock,[19] and began allowing "Acceptable Ads",[20] a program run by Adblock Plus that allows some ads which are deemed "acceptable", and the publisher pays Adblock Plus.[21]
uBlock was the original tool but was handed over to another maintainer some time ago. The original developer of uBlock, being unhappy with the direction of the tool, forked the repo and made uBlock Origin which he maintains and is often considered the better product by people here
Advertisers are already figuring out how to get around that. CNAME cloacking, proxying with same domain, etc.