Enhancement: Extending Analyze Ads Only / trackers options

[GoogleCodeExporter]

In our portal pages  - I work in a major internet portal in South America and 
in many south american countries we use adservers and trackers which are not 
recognized in the Analyze - Ads Only and Trackers filter options.

Is it possible to locally configure additional domains for the ads 
only/trackers options?

If not, I think it is a good extension that many users can benefit.

Thanks,

Marco.

Original issue reported on code.google.com by marco.pa...@gmail.com on 6 Jul 2010 at 12:56

[GoogleCodeExporter]

Original comment by mdste...@google.com on 3 Sep 2010 at 5:34

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

As I have the same question, I just read the PageSpeed C++ source code.

The filtering is based on rules made available at AdBlockRules.org in 2010, 
which site has since shut down and sent its users to EasyList.  EasyList has a 
wider range of rulesets.

Since the filters are compiled into the C++ library, I am wondering how to make 
the filters more configurable for us power users at the major portals.  I don't 
mind forking and hacking in a few new filters in a pinch, but if you C++ mavens 
have a better, more pluggable idea I'd like to hear it.

Original comment by ecortell...@gmail.com on 3 Apr 2012 at 9:39

[GoogleCodeExporter]

Hi,

I've wanted to revisit the filtering options for some time. I'd like to do a 
better job allowing users to filter common third-party widgets, for example.

Are you using Page Speed for Firefox or Page Speed for Chrome? Are your 
filtering goals general enough for us to capture in core filters or do you need 
the flexibility to specify custom filters.

Given that we're ultimately just using regular expressions we could probably 
just load text files from a custom configuration directory.

If you're using Page Speed for Firefox, another option would be to put the 
added filtering logic into a pref, again as a regular expression. Do you think 
that would be sufficient for your needs?

Original comment by bmcqu...@google.com on 5 Apr 2012 at 12:56

[GoogleCodeExporter]

Well, it's good to know that someone had the same problem and the issue is 
taken into consideration now.

We use both pagespeed for firefox and Chrome, but Firefox is more commonly 
used. I'm not sure if we need specific filters, We just need to onsider a few 
domains (tagman.terra.com.br, ppi.terra.com.br) as Adservers and don´t need to 
get into account specific request parameters, etc.

Adding the filtering logic into a pref with a regular expression is sufficient 
for us when using firefox, and adding it to an local external file for Chrome 
is not a problem also. Only technical people will use te feature, not regular 
users.

Regards,

Marco.

Original comment by marco.pa...@gmail.com on 5 Apr 2012 at 1:28