Hosts-block (ad-blocking via /etc/hosts) now in Chum

Applications
82

I’d prefer medium instead of mild.

1 Like
83

Since the latest update I cannot access tagesschau.de any longer despite it veing in the whitelist (i think it is because of the block list as it doesn’t work in the app and the Browser, and other websites do work)

Was there a change in the method for whitelisting?

1 Like
84

Which update, you mean now that it’s in main or the latest testing version or…?

You must be using some pretty tough lists that tagesschau.de is blocked in the first place.

The whitelisting mechanism itself should work normally, but I’m still working on watch-config.sh which is supposed to watch for changes in the config directory. My logic seems to be off. Maybe changes did not get applied.

I’d appreciate if you could provide output for

devel-su systemctl status -n999 hosts-block-watch-config hosts-block-forced hosts-block

although there probably won’t be much because of volatile storage.

Restarting hosts-block-watch-config might help, and starting hosts-block-forced as a last resort.

Please tell me how it goes.

85

Apparently I managed to have tagesschau.de on my blacklist as well as on my whitelist. I removed both and now it is working again.
I would have expected that whitelist overrules blacklist, because at the moment there is no gui way to reverse an accidental blacklisting of a site.
However, now it is working again, thank you for your support (and this great app once more)

1 Like
86

The file that was last changed takes precedence.

edit: it actually wouldn’t be too hard to check for such duplicates and remove the previous. With a notification.

1 Like
87

I’d say go with the Goldilocks blocking by default and let the user decide if it’s too much, too little or just right.

Glad to see this in the main Chum repo. It’ll be much more discoverable there, and I’m pretty sure plenty of SFOS users would like to discover it there.

1 Like
88

Goldilocks == medium?

89

Exactly. Like the Three Bears – the middle between the two extremes is “just right.” At least, “just right” IMO as a default starting point for the user to find their sweet spot, blocking-wise.

1 Like
90

There have been a few updates on the testing repo.

For black/whitelisting I have implemented a mechanism that will remove an entry from the other list if it was added to one.
Meaning:

  • add an entry to whitelist, with a notification
  • check if that entry is in blacklist
  • if it is, automatically delete it from blacklist, with a notification

and vice versa.

RPM will create a backup of /etc/hosts in /home when this package is first installed.

I tried to make the script that watches config files & triggers updates more robust, i.e. make sure it triggers a run even with edge cases. It sometimes triggers duplicate runs, but both the core script and apparently systemd deal with it gracefully.

The rest are internal improvements/cleanup etc.

If there are no problems/suggestions/critique I will ask for this to be pushed to the main repo.
I will also upgrade the default blocking to “medium”.

3 Likes