contain-facebook VS AdNauseam

Hm, last official release was 8 months ago. The github page looks fairly active, and there is a fix merged already for this https://github.com/mozilla/contain-facebook/pull/936 and once issue #933 gets merged, it will generate a source release for 2.3.11 at https://github.com/mozilla/contain-facebook/releases which will probably become 2.3.12 on AMO after some manual intervention.

31. Facebook Container 2.3.9 (Disabled) Facebook Container isolates your Facebook activity from the rest of your web activity in order to prevent Facebook from tracking you outside of the Facebook website via third party cookies. https://github.com/mozilla/contain-facebook

Facebook Container

This morning I looked for a similar extension for Google and I've found this fork[1] of Mozilla's extension. It's working as expected so far but I'd love for it to be officially maintained by Mozilla at some point. There is an open issue about it[2].

[0] https://github.com/mozilla/contain-facebook

Okay nevermind, that was broken due to Facebook Container https://github.com/mozilla/contain-facebook/issues/858

It’s because of Facebook container. Here is a GH issue with a fix: https://github.com/mozilla/contain-facebook/issues/867

There's an open issue and workaround for it here.

That's a Multi-Account Containers option, but ApertureNext uses the dedicated Facebook Container extension. It has an open feature request for this feature.

It does not actually clicks on the ads. It sends the request to ad server but does not execute any response from the server, so it's safe to run

https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnause...

>https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnause...

>AdNauseam 'clicks' Ads by issuing an HTTP request to the URL to which they lead. In current versions the is done via an XMLHttpRequest (or AJAX request) issued in a background process. This lightweight request signals a 'click' on the server responsible for the Ad, but does so without opening any additional windows or pages on your computer. Further it allows AdNauseam to safely receive and discard the resulting response data, rather than executing it in the browser, thus preventing a range of potential security problems (ransomware, rogue Javascript or Flash code, XSS-attacks, etc.) caused by malfunctioning or malicious Ads. Although it is completely safe, AdNauseam's clicking behaviour can be de-activated in the settings panel.

Isn't this easily detectable? XHRs are easily detectable through various headers, so it's trivial to filter out the fake traffic from this extension. Failing that, thanks to ad fraud there's a whole industry of bot/ad fraud detection firms using browser fingerprinting and behavioral analysis to detect fake ad clicks. I have no doubt that an extension that's "clicking" on every ad using XHR is going to get detected and filtered.

I'd think it's infeasible for advertisers to regularly audit third-party apps on reddit's behalf to make sure the ads they're paying to display aren't being requested but cosmetically hidden or even shadow-clicked. I'm sincerely curious if there are any example platforms that do this with their API; I can't find anything after a search.

What is your opinion on AdNauseam?

Please use this page to report issues or ask questions about Ad Nauseam. This specific issue has already been addressed:

Other than that, Libredirect and AdNauseam to be pretty neat. Allows me to avoid using certain sites directly and when I do, I mess with their ads engagement enough. A bit petty, but I'll take what I can get.