321–330 of 464 posts
Switched from Wipr 2 on my iOS/macOS instantly. Thanks!
How come? Wipr 2 is going a good job for me. Why might I prefer uBO?
Earlier quoted context omitted.
It seems to require iOS 18.6, it’s working for me after updating.
Which apparently my iPhone SE doesn’t qualify for. Every time this happens, I tell myself, “maybe it’s time to try and android phone”
Earlier quoted context omitted.
The whole point of going iPhone is not to have to deal with these kinds of situations.
So you never got gatekept by Apple from accessing a feature unless you had a specific version of the OS? Heck, even macbooks get killed every year by not allowing them to build for newer iOS versions. The whole point of Apple, one could say, IS to make sure to forcibly make you update to access a new feature. That way either you can update or you've got to buy a brand-new device.
Earlier quoted context omitted.
One time until Wipr 3, coming from a Wipr 1/2 user, just to be clear.
From what I can find, the original Wipr was released for iOS in Sep 2015 and the macOS version followed in Aug 2018. Wipr 2 is a complete rewrite and was released in Nov 2024. So, in theory, for £1.99 you could've gotten 9 years of ad-blocking on iOS and for another £1.99 the same on macOS for 6 years. And since this requires maintenance of the blocklists and associated code, I am totally fine with paying a small amo…
Earlier quoted context omitted.
> It installs, opening it is a simple message saying I need to enable it in Safari settings. Strange, but ok. I’ve made several Safari extensions for iOS, and they all have to do this. Apple provides no API for an app to enable its own Safari extension. It also has no public API on iOS to deeplink to the Settings page for enabling the extension. You just have to tell users where to go and hope they don’t get lost. (T…
Does an app for that even need to exist? Why can’t extensions be a standalone thing in the store?
1) Because then you need a whole parallel set of processes for configuring, updating, and uninstalling those things, distinct from the existing processes for apps. And you need to make that process accessible to users who may be used to everything being an app.
2) A nontrivial number of browser extensions on iOS are part of standalone apps anyway, like password managers or bookmarking tools. It'd be very strange to have both app-with-browser-extensions and browser-only-extensions, or to require some extensions to be installed and updated in tandem with a companion app for expected functionality.
Doesn't work on iOS
I also uninstalled my previous advertising blocker AdBlock Pro by selecting "Delete App" in Settings -> General -> iPhone Storage -> AdBlock Pro.
Earlier quoted context omitted.
The whole point of using an iPhone is that you don't have to update it?
No, the App Store allowing you to download an app with an extension target that doesn’t match the current system. At the very least there should be a warning or a button to update iOS if that’s possible on the current device.
Earlier quoted context omitted.
I've used Firefox Focus as an ad blocker for Safari on iOS for several years now. I don't actually use it as my browser, I just use Safari as normal, but it integrates with Safari, and seems to work well enough.
Try Brave browser on iOS, it cuts everything irrelevant without third-party apps, and you also get background media playback on locked screen (settings toggle) on youtube as "one more thing".
Earlier quoted context omitted.
Interesting... https://adguard.com/kb/adguard-for-safari/solving-problems/r... Sounds like I should direct a portion of my ire toward Apple on this.
Absolutely not. They are trying to protect you, can you imagine how awful Safari would be if it let you sideload such nasty extensions? It would be just like Chrome, absolutely no market variation to speak of! Despicable. It's really AdGuard's fault for failing to fit their functionality within the arbitrary constraints Apple decided was suitable for a runtime.
For one Safari compiles block lists to perform better, but it can be noticed at startup for big lists.
Then there is just resource constraints since the focus is mobile. Chrome on mobile notably supports no extensions.
But I do wish desktop Safari was more lenient.
(Bonus points for being inspired by Star Trek Klingon?)