I think it's pretty clear that they are discussing an App Store policy, not analytics collected by their app.
https://f-droid.org/en/packages/net.kollnig.missioncontrol.f...
Blokada's UI is without peer and so it makes for a very good "just works" for the majority (in fact, from what I know, it is the most downloaded DNS-based content blocker on Android by far).
However, it is disappointing that some of their decision-making is found wanting: https://www.reddit.com/r/privacytoolsIO/comments/papgeq/any_...
> prevents apps and browsers installed on your device from sending your private data (known as tracking fingerprints) to the Internet.
Is it doing some kind of packet inspection?
As a secondary layer of blocking I use DNS66 which intercepts DNS requests and fails them for blacklisted domains, by installing itself as a virtual VPN - essentially a cooked /etc/hosts for Android.
Would Blokada work alongside that?
For now, Blokada's utility is limited to DNS-based content blocking. It cannot and does not prevent most forms of fingerprinting.
> Is it doing some kind of packet inspection?
Yes, only DNS packet inspection, but even for the only thing it does, it is clumsy: It leaks DNS requests; that is, Blokada does not trap all DNS traffic on port 53, and it does not handle DNS queries sent over TCP. DNS66 has these same issues, too.
> As a secondary layer of blocking I use DNS66 which intercepts DNS requests and fails them for blacklisted domains, by installing itself as a virtual VPN - essentially a cooked /etc/hosts for Android.
Blokada uses the same trick (I mean, core parts of Blokada 4 code-base does bear similarities with DNS66 which preceded it... Blokada 5 however was re-written in Rust).
> Would Blokada work alongside that?
No, it cannot. But: Apps that support "DNS proxying" (like Nebulo [0]) can. It is quite an involved setup. I'd simply use Nebulo over DNS66, as it is not only more capable but also encrypts DNS traffic unlike Blokada 4 or DNS66.
> ...but you seem to be a good person to ask..
A disclosure, rather something to keep in mind: I have been accused of spreading fud by the Blokada lead developer and using it to "market" a "competitor" app I co-develop. In my defense, it wasn't / isn't fud what I spread, unless fud === uncomfortable truth.
[0] https://github.com/ch4t4r/Nebulo (fixed link, thanks u/NoGravitas)
IMO what really killed uM was major API changes by chrome and Firefox.
But yes, in the end they are both crappy vendors.
- Despite having equivalent desktop (macOS) and mobile (iOS) apps, most of our users (> 75%) use the app primarily on desktop
- Most users say the key reason for use is for privacy protection; even with Safari providing some inbuilt privacy tracking protection
- Our app is focused on providing a simple 'set and forget' ad blocking approach; so you would think the key audience would be less tech savvy users. However a large proportion of users are tech-inclined and knowledgeable users.
- A lot of tech heavy websites are some of the worst offenders in terms of tracker usage and advertising. For example, The Verge can load 3.5x faster simply by using an ad blocker that blocks the on-page trackers and ads[2]
[1] https://www.magiclasso.co/
[2] https://www.magiclasso.co/insights/difference-adblocking/