@dietrich It's still very much a work in the progress... Currently using Exodus Privacy (https://exodus-privacy.eu.org/en/) and NetGuard (https://github.com/M66B/NetGuard/) to analyse apps pre/post installing.
For most things I'm using web-apps in a browser with tracking protection. For twitter/mastodon etc this is perfectly usable, and I'm already familiar with the threat model.
@sam Haven't tried Exodus Privacy! Just started using NetGuard - seems not quite granular enough control, but not familiar enough with it yet to know for sure.
I figured out how to block requests to specific hosts in NetGuard. Just a bit hard to find and clunky to manage (per app vs global filters).
Biggest downside is you can't use private DNS or any other VPNs while using NetGuard 😦
@dietrich Yes, I didn't yet find a solution which fulfills all the requirements, though it just seems to be a UI issue. I'm thinking this could be a good Ghostery side-project, which can leverage the database of tracker owners to make this more accessible.
@sam I was thinking similar... looked through the NetGuard source and Disconnect tracker json yesterday. Does Ghostery use a different list?
@dietrich Yes, Ghostery has it's own list. This is being merged with the open source WhoTracks.Me mappings though (https://github.com/cliqz-oss/whotracks.me/blob/master/whotracksme/data/assets/trackerdb.sql). We're also collaborating with AdGuard to improve the coverage of mobile trackers (https://github.com/cliqz-oss/whotracks.me/issues/141)
@sam Oh awesome. I wonder if anyone's done research comparing different tracker lists...
@dietrich This paper compares the blocking of Disconnect to Ghostery and uBlock Origin: https://www.sba-research.org/wp-content/uploads/publications/block_me_if_you_can.pdf
macbeth.cc is one server in the network