Website recognizes that i use AdBlocker

Posting here is no longer possible, please use the forum of a filter list project, such as EasyList
Locked
volcano

Website recognizes that i use AdBlocker

Post by volcano »

Help!
I know a website that recognizes AdBlocker. It always says "Using an adblocker is unfair (...)" in big letters. I killed this text with AdBlocker but there is still a big "hole" in the design.
This is the adress: http://fbstefanie.forenhoster.net/index.php
startreking
Posts: 17
Joined: Thu Jan 15, 2009 6:13 pm

Post by startreking »

Google Translate
Ich glaube, das sollte es tun, öffnen Sie Ad-Block plus Einstellungen und klicken Sie auf Filter hinzufügen.

Code: Select all

fbstefanie.forenhoster.net##*#maintable CENTER
-- English --
I believe this should do it, open ad block plus preferences and click add filter.

Code: Select all

fbstefanie.forenhoster.net##*#maintable CENTER
User avatar
Adblock Plus Fan
Posts: 1255
Joined: Sat Feb 24, 2007 11:08 am

Post by Adblock Plus Fan »

startreking wrote:

Code: Select all

fbstefanie.forenhoster.net##*#maintable CENTER
This filter will be more optimized if you change * to TABLE
Like this: fbstefanie.forenhoster.net##TABLE#maintable CENTER


Also, someone just asked me why Table and id was better than wild card and id.

First of all, it's not always "better", the wildcard is a feature and it has its uses in certain cases.
Anyway from what I've been told, Firefox is faster when it's told to look up the Name of an element (in this case TABLE). So whenever it's possible, make sure the checkbox across the name tag is checked when you compose an element hiding rule.
Dr. Evil
Posts: 194
Joined: Fri Sep 08, 2006 3:51 pm

Post by Dr. Evil »

I think CSS engines in all browsers work from right to left - so the id is first checked, and only if it matches, the tag name is considered. So in this case, the check for the tag name is only done once at all, when the complete match is found. Also, the check for a real tag name like TABLE is probably more costly than * since that is just always true.

But CSS is so fast that you virtually never have to worry about its performance.
User avatar
Adblock Plus Fan
Posts: 1255
Joined: Sat Feb 24, 2007 11:08 am

Post by Adblock Plus Fan »

Dr. Evil wrote:I think CSS engines in all browsers work from right to left - so the id is first checked, and only if it matches, the tag name is considered.
Arrhhg...
Sorry Dr. Evil. I guess I misunderstood what you said earlier since I thought ID was an attribute:
http://adblockplus.org/forum/viewtopic.php?t=2354
Dr. Evil wrote:Checking tag names should be much faster than checking attributes. So only leave these out when necessary...
So ID is not really an attribute, but...a special attribute?
And so universal selector really use less resource than specifying tag name if you know the ID?

Then how does class perform compared to ID and the name?
Dr. Evil
Posts: 194
Joined: Fri Sep 08, 2006 3:51 pm

Post by Dr. Evil »

Adblock Plus Fan wrote:So ID is not really an attribute, but...a special attribute?
And so universal selector really use less resource than specifying tag name if you know the ID?

Then how does class perform compared to ID and the name?
Class and id are special attributes. They were introduced as a way for CSS to target a specific (set of) element(s). Therefore they are optimized in CSS. Looking up other attributes (or matching parts of an attribute with *=, $=, ^=, |=) is more costly for the CSS engine.
Adblock Plus Fan wrote:Sorry Dr. Evil. I guess I misunderstood what you said earlier since I thought ID was an attribute:
http://adblockplus.org/forum/viewtopic.php?t=2354
Actually, in one way I just said the opposite from what I said back then. That stuff about right to left only applies for different nodes separated with " ", ">", "+", "~" and so on. Inside of that, the order is different. IDs are meant to be used only once in a document, so they are looked up early. As are tag names and classes since they are pretty fast. Attribute selectors (those with the square brackets) are more costly, so they are checked after tag name, class and id. And because they are checked late and they aren't too fast, it makes sense to be more specific and specify a tag name or id in addition to the attribute selector.
User avatar
Adblock Plus Fan
Posts: 1255
Joined: Sat Feb 24, 2007 11:08 am

Post by Adblock Plus Fan »

Thanks for clarifying all of this Dr. Evil. Much appreciated!
Dr. Evil wrote:IDs are meant to be used only once in a document, so they are looked up early. As are tag names and classes since they are pretty fast.
Right, IDs are unique so I guess it makes sense to look those up first.
Then if there is no ID, is class also checked before tag name?
User avatar
Adblock Plus Fan
Posts: 1255
Joined: Sat Feb 24, 2007 11:08 am

Post by Adblock Plus Fan »

I just bumped into an interesting question, if a certain somone won't mind :P
Dr. Evil wrote:Looking up other attributes (or matching parts of an attribute with *=, $=, ^=, |=) is more costly for the CSS engine.
Sometimes it's not necessary to include the value of an attribute to pinpoint an element.
In that case, wich one is faster to lookup:
[title]
or
[title="blah blah blaaah"]
?
Dr. Evil
Posts: 194
Joined: Fri Sep 08, 2006 3:51 pm

Post by Dr. Evil »

Adblock Plus Fan wrote:Then if there is no ID, is class also checked before tag name?
I don't know. But class and tag name are both fast, so I wouldn't care about that.
Adblock Plus Fan wrote:In that case, wich one is faster to lookup:
It doesn't really make a difference. The check whether an element has an attribute will always have to be done to check the attribute value. So the check whether the attribute value really matches is only done once when the rule actually matches. That's a rare case you don't have to optimize. So when the attribute value will make the rule more specific I think its safer to use it as well.
Locked