Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

On Android you can use Firefox + uBlock Origin.


In addition to uBO, I also use TrackerControl.

https://f-droid.org/en/packages/net.kollnig.missioncontrol.f...


This is the way. Although the built-in blocker in "strict" mode does a darn good job as well with a rare site breakage


Add Blokada + Newpipe to the mix as well.


I don't recall ever having heard about Blokada before, but looking it up now it doesn't seem recommended: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/8536


(I created that merge request)

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_...


Forgive the questions, but you seem to be a good person to ask.. How does Blokada actually work? Its FAQ claims it:

> 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?


> prevents apps and browsers installed on your device from sending your private data (known as tracking fingerprints) to the Internet.

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)


Github link for Nebulo appears wrong: is this the correct one?

https://github.com/Ch4t4r/Nebulo


Would you mind to suggest any alternative to Blokada? Thanks!



Thanks for the info!


And uMatirx, but Firefox put stop to that one.


Pretty sure Firefox did no such thing, instead IIRC the developer (gorhill) of both addons (uMatrix and uBO) realized that uMatrix was pretty much redundant given the options available in uBO and thus archived uMatrix.


We had a HN discussion where users brought up situations where uB could not replace uM.

IMO what really killed uM was major API changes by chrome and Firefox.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: