Is this kind of thing why uBO added the localhost / localnet filter? Or does this go beyond that?
I think so.
Some browsers for Android have blocked the abusive JavaScript in trackers. DuckDuckGo, for instance, was already blocking domains and IP addresses associated with the trackers, preventing the browser from sending any identifiers to Meta. The browser also blocked most of the domains associated with Yandex Metrica. After the researchers notified DuckDuckGo of the incomplete blacklist, developers added the missing addresses.
Firefox with the EFF Privacy Badger extension.
That is all.
It’s not all. Not by a long shot.
Any recommendations for additions to the arsenal?
It depends entirely on your threat model. Start with privacyguides.org
For anyone simply not wanting to have their data scooped up en mass, you still have to defeat IP triangulation, browser fingerprinting, and shadow profiling. Our data is extremely valuable to some people, and they go to great lengths to get it.
