[EasyList] Ads in Domains Hosted in Google Apps

em4r1z · Post by **em4r1z** » Tue Jun 30, 2009 4:00 am

I've been using AdBlockPlus with the EasyList and EasyPrivacy filters for a couple of years now and the ads of Gmail and domains hosted in Google Apps were blocked, till last week (Thursday, probably). These domains use the Spanish interface of Google Apps and no administrative changes were made to the service or the interface.

I haven't been able to set up the filter or trace the change (the source code is almost empty). Any ideas about this?

em4r1z · Post by **em4r1z** » Tue Jun 30, 2009 3:01 pm

I just checked and the text ads also appear in YouTube's Spanish interface now. This is relevant because Google is the provider of those ads, just as in Gmail and Google Apps.

I'm not sure if YouTube's interface is set by IP, but one can select the language in the top left corner, or set the preferred one within Firefox's preferences. In case someone wanted to try.

Wladimir Palant · Post by **Wladimir Palant** » Tue Jun 30, 2009 3:22 pm

I changed YouTube to Spanish/Spain but don't see any ads. Can you upload a screenshot to http://imageshack.us/ and post it here?

em4r1z · Post by **em4r1z** » Wed Jul 01, 2009 5:28 am

.....

The first thumbnail doesn't show text ads because the search didn't contain relevant information for Google (axwell leave dirty), the second one does (voodoo sunglasses club).

Here's the source code of the page with text ads: http://de.pastebin.ca/1480319
Relevant section starts at line 346.

em4r1z · Post by **em4r1z** » Wed Jul 01, 2009 5:49 am

That's a thumbnail of Google Apps text ads.
Here's the source code: http://de.pastebin.ca/1480334 Many words were replaced by [replaced] for privacy reasons.
The relevant sections starts... nowhere!

Wladimir Palant · Post by **Wladimir Palant** » Wed Jul 01, 2009 7:46 am

Aaargh... It's Debian. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525938
The official Firefox build works fine, it's only IceWeasel that has this problem.

em4r1z · Post by **em4r1z** » Wed Jul 01, 2009 3:32 pm

My mistake. I'm sorry, had I stated I was using Debian Testing with Iceweasel, this issue would've been clarified ages ago.
I read the bug you mentioned (and related ones), and the problem lies in the xulrunner package, for Iceweasel hasn't been updated lately.

I hope this gets corrected in the next update. Thanks, mate.

Wladimir Palant · Post by **Wladimir Palant** » Wed Jul 01, 2009 4:22 pm

Supposedly it is XULRunner 1.9.0.11 - but it seems to be missing at least one patch from the official XULRunner 1.9.0.11.