3 ms·
The reason these APIs are being removed are to improve the privacy of users. Apple recommends all adblock extensions now use the content blocking API which is
by happybuy 8y ago
The reason these APIs are being removed are to improve the privacy of users.
Apple recommends all adblock extensions now use the content blocking API which is superior from a user privacy perspective. When using the content blocker apis, the extension cannot view or read which web pages are visited. Prior extension APIs had full access to browsing history (which obviously can be easily abused).
The content blocker API is different but does allow full featured and sophisticated adblockers. I know because I create one which is very efficient, effective and free - Magic Lasso Adblock (https://www.magiclasso.co/ https://www.magiclasso.co/)
- kkarakk 8y agoas usual apple doing weird things that only people deeply invested in their platform will bother learning.
- saagarjha 8y agoWhile Apple has been guilty of this, but I think in this case this has actually improved their platform. I’d really like for the API they are proposing become a web standard, but unfortunately I doubt it would ever do so…
- Karunamon 8y agoExcept that API kills one of the main use cases - live blocking annoying stuff that's already on the page. Apple's gimped API, as far as I can tell, offers no way with the user to interact with the plugin. Meaning that if the blocker misses something (and it will), I have no way to deal with it. This "privacy" canard is just Apple being Apple and punishing users in the name of full control. The #1 and #2 most used adblockers by everyone have no legitimate privacy concerns.
- snaky 8y agoThat's Apple's model - users cannot make their own decisions.