Stubborn frame...
Two words
Ooo. Ah.
Thank you, Dr. Evil and Stupid Head.
I dumped Filterset.G, added the element lists, and, sure enough, the big bad box was gone.
Then, with what you told me, I was able to remove the small "related links" box which still appeared on the print version of eweek articles. Got it right the first time, rawr. In this case finding the thing I need to block is easy because I'm an interface guy and spend most of my time in HTML and CSS, so what I needed was the syntax.
Thank you, thank you!
Thank you, Dr. Evil and Stupid Head.
I dumped Filterset.G, added the element lists, and, sure enough, the big bad box was gone.
Then, with what you told me, I was able to remove the small "related links" box which still appeared on the print version of eweek articles. Got it right the first time, rawr. In this case finding the thing I need to block is easy because I'm an interface guy and spend most of my time in HTML and CSS, so what I needed was the syntax.
Thank you, thank you!
@Tadiew: No, in my optinion Filterset.G has too many issues. It makes heavy use of complicated regular expressions with the consequence that filter processing is slow (benchmark shows 80 ms instead of 20-30 ms for most subscriptions). This also has the consequence that issues are difficult to locate and to fix, that's why Filterset.G uses whitelisting instead. The problem with this is then that whitelisting can't be overridden, it happened several times in the past that Filterset.G prevented blocking of actual ads. Finally it requires a separate extension to update, for all other filter lists Adblock Plus can do itself.
So my recommendation is EasyList, it is a perfectly good replacement for Filterset.G that also happens to have a responsive maintainer.
So my recommendation is EasyList, it is a perfectly good replacement for Filterset.G that also happens to have a responsive maintainer.
Thank you. I appreciate advice on subjects I'm a total blank on very much. I have the EasyLists in AdBlock, so I think I finally have FF 2.0 the way I'd like it to be.Wladimir Palant wrote:@Tadiew: No, in my optinion Filterset.G has too many issues. <snip> So my recommendation is EasyList, it is a perfectly good replacement for Filterset.G that also happens to have a responsive maintainer.
About Filterset.G...
Those whitelisting filters are so bad, it currently has 37 more or less bad whitelisting filters.
Like this: @@.buy.com
because: .com.au (Australia), .com.cn (China) and .com.sg (Singapore) are whitelisted too.
And this: @@ads-pipe.com
because it can be: downloads-pipe.com
Anythingads-pipe.comAnything
There is another reason why it's better not to whitelist with @@.buy.com, it's little hard to explain because my english sucks, but i try...
Like if you whitelist google with: @@*.google.com/*
and then use google.com, type jokeroo and go to first result (if it's Jokeroo.com).
ads.jokaroo.com script is whitelisted, now it seems to load doubleclick ad.
But my point is, that it could load some ads that filterlist does not block.
Filterset.G also has Regular Expressions whitelisting filters, like:
I don't know what that means, maybe it whitelistes random things 
I think only right way to whitelist is with full domain and if there must be wildcard, it's better be after that domain, like:
@@|http://domain.com/*
but it's always better if it's more like:
@@|http://domain.com/somethingmore*
@@|http://domain.com/somethingmore*plusevenmore*
And if it needs to be item whitelisting rule, then:
@@|http://domain.com/*$~document
@@|http://domain.com/somethingmore*$~document
And these are the filters i use:
@@|http://adisney.go.com/disneypictures/ca ... ds/*$image
@@|http://ak.buy.com/db_assets/ad_images/*.gif|
Those whitelisting filters are so bad, it currently has 37 more or less bad whitelisting filters.
Like this: @@.buy.com
because: .com.au (Australia), .com.cn (China) and .com.sg (Singapore) are whitelisted too.
And this: @@ads-pipe.com
because it can be: downloads-pipe.com
Anythingads-pipe.comAnything
There is another reason why it's better not to whitelist with @@.buy.com, it's little hard to explain because my english sucks, but i try...
Like if you whitelist google with: @@*.google.com/*
and then use google.com, type jokeroo and go to first result (if it's Jokeroo.com).
ads.jokaroo.com script is whitelisted, now it seems to load doubleclick ad.
But my point is, that it could load some ads that filterlist does not block.
Filterset.G also has Regular Expressions whitelisting filters, like:
Code: Select all
@@/[-/]\d{1,3}ad\d{1,3}[-/]/

I think only right way to whitelist is with full domain and if there must be wildcard, it's better be after that domain, like:
@@|http://domain.com/*
but it's always better if it's more like:
@@|http://domain.com/somethingmore*
@@|http://domain.com/somethingmore*plusevenmore*
And if it needs to be item whitelisting rule, then:
@@|http://domain.com/*$~document
@@|http://domain.com/somethingmore*$~document
And these are the filters i use:
@@|http://adisney.go.com/disneypictures/ca ... ds/*$image
@@|http://ak.buy.com/db_assets/ad_images/*.gif|
A "-" or "/", 1 to 3 digits, "ad", 1 to 3 digits, and another "-" or "/". So, something like "blah/39ad6-something.gif".Fox wrote:Filterset.G also has Regular Expressions whitelisting filters, like:I don't know what that means, maybe it whitelistes random thingsCode: Select all
@@/[-/]\d{1,3}ad\d{1,3}[-/]/
Matt Nordhoff