Code: Select all
*||ad_type=pop||
! replaces:
*?ad_type=pop&*
*&ad_type=pop&*
*&ad_type=pop|
Code: Select all
*||ad_type=pop||
! replaces:
*?ad_type=pop&*
*&ad_type=pop&*
*&ad_type=pop|
No, with the current definition || would be accepted at the end of the expression only. However, I do agree that this one probably cannot be called an anchor at all, it is a placeholder for a separator character (like * is a placeholder for any characters). Looking at the US keyboard layout, there aren't that many options. So maybe "^adtype=pop^", "||example.com^" and "||example.com/foo^"?Dr. Evil wrote:So would this work?Code: Select all
*||ad_type=pop|| ! replaces: *?ad_type=pop&* *&ad_type=pop&* *&ad_type=pop|
I don't think it should be default, many sites use a different subdomain for their ads and currently the third option (http://ads.example.com/*) is what you want to block then and not the whole site (||example.com/*).Wladimir Palant wrote:* Filter composer should be able to use flexible anchors (should that be the default for all suggestions?)
That would be very nice for adservers.Wladimir Palant wrote:"||example.com^"
In that situation I only see gain in ||ads.example.com/* becoming default.Ares2 wrote:I don't think it should be default, many sites use a different subdomain for their ads and currently the third option (http://ads.example.com/*) is what you want to block then and not the whole site (||example.com/*).
There's one disadvantage I can think of if this is implemented by default, some filters might become too short to be optimized if you remove http:// with this flexible anchor.Wladimir Palant wrote:* Filter composer should be able to use flexible anchors (should that be the default for all suggestions?)
OK, I thought "use flexible anchors" means actually using it. This way it doesn't make any difference to the current suggestions anyway (except if you drop "www" of course), so go for it.Wladimir Palant wrote:Ares2, the default suggestion would be "||ads.example.com/foo/" for "http://ads.example.com/foo/bar".
I guess you're right, this will only happen extremely rarely.Wladimir Palant wrote:the case where the user gets a very short domain name *and* wants to block everything from that domain should be very rare.
Code: Select all
.doubleclick.net/*;cue=pre;
.doubleclick.net/adi/
.doubleclick.net/adj/
.doubleclick.net/adx/
.doubleclick.net/pfadx/*;ord=
.doubleclick.net/pfadx/*.mtvi/
.doubleclick.net/pfadx/*.mtvi/
.g.doubleclick.
/ad.doubleclick.net/ad/*
"||ads.example.com/foo/"Ares2 wrote:OK, I thought "use flexible anchors" means actually using it. This way it doesn't make any difference to the current suggestions anyway (except if you drop "www" of course), so go for it.Wladimir Palant wrote:Ares2, the default suggestion would be "||ads.example.com/foo/" for "http://ads.example.com/foo/bar".
Yeah, I know I should have said "almost", but these are very rare cases.Fox wrote:"||ads.example.com/foo/"
Blocks:
http://ads.example.com/foo/
https://ads.example.com/foo/
mms://ads.example.com/foo/
Yep, it's covered by (?:[^\/]+\.)?Ares2 wrote:BTW, will ||example.com/ also block ht*p://foo.bar.example.com/1.gif (more than 1 subdomain)?