grimd and subdomains

[myxalov]

Our blacklist has domains such as "*.google.com"
Grimd don't understand this form as subdomains.
Also if domain listed as "google.com", and domain "www.google.com" is working.

[looterz]

Sorry the response has taken so long on this issue. It is a fairly annoying issue to deal with, but something I would like to fix for an upcoming release. I will look into some methods for pattern matching domain names and see what I can come up with.

[emdioh]

I have a tentative implementation.
Myxalov: can you clarify what you mean with your last line: Also if domain listed as "google.com", and domain "www.google.com" is working. ?
Thanks.

[emdioh]

#24 adds support for globs

[myxalov]

Sorry, I meaned that domain "www.google.com" isn't working if domain listed as "google.com".

[emdioh]

I see. I'm not sure that it should, though: iiuc both google.com and www.google.com are valid domain names and could correspond to different services.
Would the globbing support solve your usecase?

[elico]

@emdioh @looterz I think that using .google.com should catch all while google.com should catch only google.com with a switch. to turn this function on and off.

[photostorm]

Is this still a issue or was it fixed with globs support?

[elico]

@looterz I have seen something interesting about such a subject:
*.google.com would catch 111.google.com 11.google.com but not 1.111.google.com

And:
**.google.com would catch any subdomain in any level.

What do you think? @photostorm ?

[xgocn]

I have "sub.abc.com" in the whilelists and "*.abc.com" in the blacklists, what would happen?