@mipstian Hello, I recently launched the Wipr app đŸŽ”for the first time in foreverđŸŽ” and was surprised it needed a block list update. A Help notification thingy also advised not quitting the app from the switcher.

After refreshing, some niggling ads leaking through went away.

This makes me rethink how I interact with Wipr. Should I be in the habit of launching it from time to time? (Or, perhaps, have a shortcut automation to launch it after any restart?)

@atlauren if you don't quit it, it will be able to refresh automatically!
@mipstian I’ve just attached a “Launch Wipr” shortcut automation to “when plugged in”. :D
@atlauren that’s a lot of waste but you do you 😅
@mipstian but
 if it’s never launched it won’t be in the background
 right?
@atlauren it doesn’t need to be. It just needs not to be killed by the user.
@mipstian ohhhhhh!

@mipstian I think I’m forever confused by the distinctions between the app-as-interface and the browser extension(s).

Like, if I use it all the time and update from App Store routinely, why would the refresh have been lagging?

(Sorry to be That User)

@atlauren Apple has tried really hard to kill the idea of a browser extension and wrap everything in an app, but lots of users (I suspect those who have been using extensions before the App Store) are resisting.

You don’t use Wipr all the time I’m assuming, you’re using Safari. Which has no consequence on whether Wipr can refresh in the background.

Sometimes people ask me how do you uninstall Wipr Legacy and when I say “like any other app” they don’t believe me đŸ€·â€â™€ïž

@mipstian I wonder if I’m overthinking this
 and if I happen to see an escaped ad, THEN launch Wipr and check for a refresh. đŸ€Ș
@atlauren you don’t even need to do that, just don’t kill the app đŸ˜