How "@@|" and "~domain.com" rules work?


konieckropka

Recommended Posts

In subscribed global rules we have few lines that I do not understand..

What does "@@|" and "~domain.com" rules mean ?

From this

!special MX3BUG-9684

@@|http://image.tuku.china.com/*

@@|http://tuku.*.china.com/*

@@|http://news.china.com/*

!White

@@|*.qinsmoon.com/*ad*

@@|*hnair.com/gg/*

@@|*crossdomain.xml

@@|*.css

@@|*/logo/*

@@|360buy.com/uploads/*

@@|51job.com/*

@@|a.5d6d.com/*

@@|*click.cnzz.com/ad_quanjing/source/css/*

@@|*union.bokecc.com/*

@@|*pic.top100.cn/AdImg/*

@@|shangcuwang.com/ads/*

@@|*/search/*

@@|*/so_*/*

I guess it is something about Whitelist?

So does it mean everything that after @@| is not blocked despite another rules?

like

##div

@@|div#id2

will block all div's with id= startign with letter "i" but not

?

And also how rule ~domain.com#div works?

There are few lines in subscribed global rules like:

~fastcom.com.cn###ad1

~fastcom.com.cn###ad2

~fastcom.com.cn###ad3

~taobao.com,~ntsms.palmyou.com##

Any help with those two?

Link to comment
Share on other sites

konieckropka replied at 2013-6-28 05:50 back.gif

So why both of them doesn't work (or at least seem to not work when created in users-specific list) ...

if you're blocking it and also whitelisting it, simultaneously, it will contradict, and I'd think that'd mean it stays as unblocked, though I may be wrong.

It might be the syntax if everything, doesn't mean that the @@| is not correct. It might be after that part.

At least.....I can't confirm. Then again, I don't use whitelists much because if I don't want something blocked, then it's not blocked in the global subscribed rules, and I just don't put a rule to block them, essentially accomplishing the same goal as a whitelist. If I ever need to block an element without blocking a sub-element, I look for work-arounds using other element IDs, or css rules, etc., so I can block one without the other. If the sub-element is not the same element as the parent element, that is.

Often, however, I have come across instances where putting in a URL as...well, something to contrarily, block, it will not recognize it and will remain unblocked, unless I put in the whole path. Variables somehow aren't ALWAYS working for me. Some of those seem to include variables. Might be a problem there, but if the variables aren't included, you'd have to block every file in that URL with that part of a path. And at least for js files, a lot of sites' js files are dynamic in that if you block one, they embed another; so essentially in those cases, it'd be impossible to block all, because they're limitless, unless you block the whole path that includes every js file at which they have it located, consistently.

cooltext.png

Link to comment
Share on other sites

  • 4 weeks later...

Archived

This topic is now archived and is closed to further replies.