Privacybadger: The problem with wired.com

[terrorist96]

As of right now, the following cause wired to throw an anti-adblock message:

pagead2.googlesyndication.com

I'll expand on this as I find more. Due to the nature of Privacy Badger blocking different things on different Chrome profiles (since it hasn't learned yet), tracking down everything that triggers the warning will take some time.

[cooperq]

I think that the real solution here involves talking to wired and figuring it out together.

[terrorist96]

Good luck with that. They seem deadset to ruin the experience of anyone with any adblocker or privacy related extension.

[terrorist96]

Did you try talking to wired?

[cooperq]

These things take time...

[ccoenen]

Thanks for documenting this, putting pagead2.googlesyndication.com on "no cookie" solved the problem for me, too! I don't mind them showing me ads (after all, they have some of the less annoying ads) I _do_ mind 22 tracking systems watching me reading their article.

[cooperq]

Nice workaround! Thanks for catching that. It makes sense why wired would block something blocking that. I wonder if this could be solved with #400? We should look into it.

[floe]

Hm, any news on that? I don't actually have pagead2.googlesyndication.com in my block list, but Wired still annoys me with the blocker...

[jacobped]

@floe I changed securepubads.g.doubleclick.net to no cookie and it worked after a site refresh.

[floe]

Thanks, that did the trick.

[cooperq]

Hmm, perhaps I should consider a way to give the user an option to automatically do that when they visit wired.com, would have to consider how best to implement this. Any ideas?

[terrorist96]

400?

[ghostwords]

Let me know if this is still an issue.

[terrorist96]

@ghostwords It's still an issue. Please reopen.

On a test profile with only PB active (I also sent the error report via the "did pb break this site" button just a few minutes ago; can you take a look?):

Note: sometimes it takes a lot of scrolling and opening different articles to trip the warning.

[alanton]

I have tried to reproduce this without success. Is it possible that this message is being triggered by another extension?

[terrorist96]

Yeah I'm having trouble reproducing it now too. Though it was confirmed earlier that having only PB was enough to trigger it (see the post above yours). Something must have changed on wired's side.

[ccoenen]

Yes, it's no longer an issue for me, too.
They still use a ton of trackers and ad networks (and other third party technologies), but I don't get the overlay any more.