How to install this on iOS? I don’t see it on the App Store.
1 Like
It might not be available in the store yet as it’s still in beta, but it is now approved (notarised) by Apple.
Edit: I have no idea whether all Safari extensions are also available on iOS
Sorry, that’s likely false since even uBOL filters are converted to content blockers rules.
1 Like
It’s still being reviewed by Apple, but it will get posted on testflight first.
I actually believe we shouldn’t remove AdGuard recommendation. In fact, IMO we should even recommend it as a MV3 extension for Chromium browsers.
The reason is AdGuard is much more powerful than Ublock Origin Lite (ubol). For example, in Addguard you can add your own cosmetic/procedural rules (at least on Chromium), while ubol doesn’t allow you to (it might be added in the future).
Also, Adguard will allow you to add custom lists in their next big release (this will necessitate enabling Chrome dev mode though).
4 Likes
Ublock lite is out on TestFlight for Safari if anyone wants to give it a try. I tried it out. It still needs some work. I’ll stick with Adguard for now.
3 Likes
One major difference between uBOL and AdGuard is that AdGuard is using the native content blockers function in Safari in addition to an extension, while uBOL is only an extension.
This is major because extensions on iOS do not run in PWAs or web previews but content blockers do (on MacOS extensions do run in PWAs).
So if only using uBOL on iOS, there are no content blocking capabilities in PWAs. This would go against the usual recommendation to use PWAs over native apps for privacy.
Isn’t “Adguard for Safari” an exension? I am a bit confused here.
There are two ways an app can go about blocking content in Safari.
One way is through using the native “content blockers” app extension built into Safari. These are the classic rules lists that can block cookies, loading certain things, and can hide elements from the page. Content blockers cannot see anything on a webpage or report anything back to its app. Content blockers predated Safari supporting extensions.
Extensions are more robust and can do
more things like view the contents of a webpage and run code. These can be enabled on a per site basis. Extensions can interface with its app.
Examples of extension functionality that is not possible with content blockers include a password manager inserting a drop down account selector on login screens and blocking ads on YouTube.
Extensions and content blockers run in all Safari windows on MacOS. In Safari on iOS, extensions only run in the main app and no not run in PWAs or web views. Content blockers do run in PWAs and web views.
AdGuard for Safari uses both content blockers and an extension. The content blockers are used for the usual blocklists and the extension is used for more complex blocking. Here is the info from AdGuard on the difference.
uBOL only uses the extension function so its blocking capabilities are limited in PWAs on iOS.
1 Like
Not sure. I heard that AdGuard for iOS is MV2 but couldn’t confirm it myself.
This is off-topic and has already been discussed Proposal: Remove uBlock Origin and update criteria for browser extensions
1 Like