TL;DR: could a Jolla Dev jump in an explain the bugs that cause harbour-defender <=0.4.0 to get black-listed so the community can fix it ?
REPRODUCIBILITY (% or how often): Always
BUILD ID = OS VERSION (Settings > About product): 18.104.22.168
HARDWARE (Jolla1, Tablet, XA2,…): XA2 (but is not hardware-dependent)
REGRESSION: (compared to previous public release: Yes, No, ?): Yes, it’s new in Pallas.
Lots of people hate having ads taking up their (limited) mobile bandwidth and overall degrading the browsing experience.
A possible to handle this is through hostfile.
Defender by nodevel is one such application that offer a GUI to select and automatically update the hostfile based on well known blacklists.
For some reasons, since SFOS 22.214.171.124 Pallas, harbour-defender has been added to patterns-sailfish-app-blacklist. I would be great if some Jolla Dev could jump in and explain which bug inside harbour-defender makes it incompatible and worthy of a blacklist, so we can fix it.
STEPS TO REPRODUCE:
- Try installing harbour-defender from openrepos.net
Harbour-defender gets installed and we can use it to block ads.
patterns-sailfish-app-blacklist blocks installation of harbour-defender and ads are still inflicted upon us and our bandwidth.
harbour-defender’s source code is available on Github, so it should be possible fix whatever trouble cause it to be put on the blacklist.