AdNauseam
AdNauseam copied to clipboard
dhowe
AdNauseam not showing ads blocked or clicked in extension
Describe the issue
No info on ads blocked or clicked even when new firefox profile created with only adnauseam installed on any site. However ads are still being blocked. NOTE: if you are having a problem where ads are not collected, please FIRST TRY to create a new new Firefox profile as described here. A corrupt Firefox profile is the most common cause of this issue.
Screenshot in which the issue can be seen
Steps for anyone to reproduce the issue
(Please be as detailed as possible) Install adnauseam on firefox (same result happens for me on microsoft edge again with no other extension).
Your settings
- OS/version: Windows 11 pro 22H2
- Browser/version: Firefox 118.0.2(64-bit)
- AdNauseam version: 3.18.0
- Other extensions you have installed: None
- AdNauseam settings: "block ads, "click ads" "block malware"
Your filter lists
Default lists.
Your location/country
(If the issue is website specific, knowing your approximate location will help us to reproduce it)
** For adult or potentially offensive sites/ads, please add a [Content-Warning] tag in the title to warn developers the ticket may contain such material.
hey @AK220011 unfortunately now on all websites we can collect ads successfully, websites such as youtube/facebook/instagram have quite complex ad rendering structures which makes it hard for us to collect them.
If could share with us what website you visited that you expected ads to be collected would be helpful.
@dhowe it seems users are often confused by our messaging when no ads are yet collected. Maybe we should show on our menu, like ublock, how many ads were blocked, and how many of those we managed to collect? Maybe it could be displayed on the top part of the menu?
do we have access to the number that ublock shows? this may be a bit confusing as well with 4 numbers shown (clicked, collected, blocked and vault). I've added @mushon to this ticket to get his take
We have it yes. But just that many users have had the same confusion as in this issue.