This feature request is about adding a blocking history / log with the goal to be able to easily see which domains and apps are accessed / blocked most often and to be able to tell which of then should be blocked or unblocked.
The idea is to be able to identify apps which are "the biggest offenders".
I truly love this app. However, after 3 days of use, I'm still getting a significant number of ads coming through. It would be really amazing, if, when ads are able to slip through, you could have a switch or checkbox that you could easily engage. It would add the source, and any other pertinent info necessary to block transmission of those ads, forever.
adaway
advised
For apps wich still display ads an option to record all traffic and list all the connections and hosts might be helpful to find the domain/host adress displaying the ad. Of course finding that particular host showing the ad might still be a piece of work. But I would be able to progressively block the listed addresses until I get the ad domain.
This is a must have for me! I love Blokada, but a log of blocked stuff (url, date time, matched list and if possible (root feature?) the app responsible for the request.
Would be even better if there was some kind of data visualization in-app. Could be a great way to share what's really happening on a phone over social media.
It would be good if you can choose in which apps you want Blokada to work
Just to have it on this feature ticket as well:
As Hosh explained on issue 178 it would be very useful to see which rule _of which list_ is blocking something.
Very interested in this too. Just moved from iOS to Android and this is my favourite ad blocker so far, this is the only thing it's missing.
It's very useful to see what domains slipped through (and what was definitely blocked) so you can add it to the blacklist. Notifications are nice, but it's annoying having them on constantly - and just not as easy as seeing a time stamped log file.
The only app I have experience with is AdGuard on iOS (and one other that wasn't as good) and despite being a bit ugly looking, they did do quite a nice job of it.
Another vote for the log file at least; currently, selectively debugging what to allow and what to reject is pretty difficult.
Most helpful comment
Another vote for the log file at least; currently, selectively debugging what to allow and what to reject is pretty difficult.