Your logic is utterly flawed.
Besides, it’s a pain in the ass and you might get banned so you end up working fewer hours for the website.
People with careers are getting cancelled because of their opinions published online. Nudging people to identify themselves online is inviting them to dig a grave
Hence calling it a feature, not a bug is rather misleading. Since you went and installed plugins understanding that it might and it will affect your workflow.
Many benchmarks proved that. Here's one: https://whatsoftware.com/10-ad-blocking-extensions-tested-fo...
Maybe it's lacking a setting to toggle this (Suspend all network until lists are loaded doesn't control this behavior), but I wouldn't want to load pages full of ads on mobile simply because the app got killed.
The real issue for me is my phone killing applications when it has both battery and memory available.
But it has some pretty big downsides, the battery is small, and it is rather bad at this point of life. The audiojack has been oversized by constant use and barely holds now the headphone, stuck in Android 12.
I know I'm in the minority, but I consider both of these behaviors to be a very bad and extremely frustrating idea.
Edit:
Yeah, disabling prefetch:
> This will ensure no TCP connection is opened at all for blocked requests: It's for your own protection privacy-wise.
uBlock holds itself (ideally) to a higher standard than not executing js or hiding an element, it tries to prevent the network connections from even taking place. This is for browser prefetching that happens on many pages even after the environment and extensions are fully loaded, in many different contexts, to speed up requests by having the binary payload of the response already available in cache before it is needed.
Lately, I've noticed Chrome being really aggressive about this.
[1]: https://arstechnica.com/gadgets/2023/02/chrome-110-will-auto...
This "bug" is in Safari/Webkit too, stop it with the conspiracy theory.
https://www.theverge.com/2023/10/26/23933206/google-apple-se...
My workaround is to use Tor. That sails right through.
Excellent job. My tax dollars at work.
> Firefox will wait for uBO to be ready before sending network requests from already opened tab(s) at browser launch.
> In Chromium-based browsers, this is not the case. Tracker/advertisement payloads may find their way into already opened tabs before uBO is ready, while Firefox will properly filter these.
That’s a hell of a “bug” in Chromium, that blocker initialization has a race condition with restoring the last opened tabs. What a weird little “accident” that Chromium just moves forward and loads all the trackers, “oopsie”. I wonder which kind of promotion the engineer who made that “mistake” has been awarded.