Ad blocking on SFOS

What do you all use for AdBlocking? Is there any better way than updating host files manually?

Preferably something that also works for thr Android subsystem.

2 Likes

There is a package in chum i think.

This needs to be an extension in the browser but our browser doesn’t cut it for the modern web.

1 Like

I use Appsupport, Fennec from F-Droid and uBlock Origin with the settings recommended on Kuketz blog.

This works very fine on SailfishOS. Yes, it’s a workaround and not a solution, but this way one can have a working browser on our beloved SailfishOS within minutes without struggling with outdated Sailfish Browser.

Stock Browser remains still usable and you can manually set your preferred default browser.

8 Likes

I was more interested in system wide solutions, I use Firefox with extensions anyway.

2 Likes

Sailfish-browser should ship with uBlock by default.

2 Likes

I use Hosts-block (ad-blocking via /etc/hosts) now in Chum:testing which works perfectly!

5 Likes

I Have using uBlock Origin many years on PC. It is very good.

2 Likes

I found the best system-wide solution to be Privoxy with the ab2p plugin (both on Chum). You need to set it as a global proxy in Settings and in the about:conf of Sailfish Browser, instructions are available on the GitLab repository.

For me the filters block most in-page ads in Sailfish Browser, even video ads on m.youtube.com and in the Duolingo Android app (not sure if that’s related to Privoxy) so I’m happy with it.

7 Likes

Good to know there’s at least one user apart fom myself! :smiley:

7 Likes

Well I feel I might make it two to test it out


Lately, I’ve been using AdGuard DNS, which works pretty well across both the main system and the Android layer. You can also try setting up Blokada inside the Android subsystem—it’s lightweight and does the job nicely without messing with system files.

1 Like

3 Likes

Is it possible to set a custom DNS resolver? I am using an ad-blocking one on Android that works quite well.

Nice one :+1:

I was not aware of this thread, just now accidentally with this vid for Defender.
There is one misinterpretation/misunderstanding in the video about the deleting of cookies. This is not triggered by the (quite new configurable) update interval. But I already have this stored on my mind as feature request to make this video correct. :smiley:

The other one is host-block (by @ohnonot ), more script oriented without GUI.

And of course the already mentioned privoxy of @nephros which works a bit more modern with rules, not just plain domain blocking.

4 Likes

You know there is one more :wink:

What exactly do you mean?
On older sfos connman was responsible for resolving dns.
On newer (>=5.1) it is systemd-resolved.
You may edit /etc/systemd/resolved.conf.
Or also simply edit the WLAN settings with a DNS server.

Sorry to be unclear. I am coming from Android which offers a global “private DNS” option where a custom DNS server can be configured. resolved.conf seems the way to do that in SailfishOS/Linux

Thanks, I’ve been bookmarking post and likes so when I receive my J2, I can quickly look back at the tips on how to set it up. Would be nice to see a video for new users to SFOS on top things to consider such as staying native or if also using AAS


Thanks for the mention!

It’s hosts-block btw.

And while it is indeed a shell script, one doesn’t really need to do anything. It works ootb (medium strength) and can be configured on the fly through editing a config file.

1 Like

And “corrected” Defender to match the explanation about automatic cookie deleting on update :smiley:
v0.9.9 on chum:testing