DBLP Computer Science Bibliography [$domain]

[gst]

EasyPrivacy blocks the "CompleteSearch" of DBLP at http://dblp.mpi-inf.mpg.de/dblp-mirror/index.php (the autocomplete box on the right).

The matching rule seems to be:
/logging.js$domain=~banking.ing-diba.de

as DBLP includes the following script:
<script type="text/javascript" src="http://dblp.mpi-inf.mpg.de/autocomplete ... "></script>

/gst

[rick752]

How does the domain exception rule do anything for that page ... they are not the same. It does nothing.

[eighty5cacao]

rick752: Are you sure you are reading the original post correctly? The OP said, "The matching filter seems to be..." This means the filter that is matching the script, as opposed to a suggested filter to fix the problem (which the OP never gave).

I can reproduce the OP's problem from here. The /logging.js filter no longer has the $domain parameter the OP mentioned, but that doesn't matter for obvious reasons.

[rick752]

I understand that ... but allowing "banking.ing-diba.de" does not work on a domain that is called "dblp.mpi-inf.mpg.de".

I was just wondering whether this is actually from somewhere else. What is that site for anyway? Is it a site worth fixing here ... or something that the user should just whitelist himself?

[eighty5cacao]

I edited my post while you were writing your reply.

"Allowing "banking.ing-diba.de" does not work on a domain that is called "dblp.mpi-inf.mpg.de"" is exactly why there is a problem here - the script is still blocked.

If the OP was not clear, the symptom is that the autocomplete function doesn't work - the box itself is visible regardless.

[rick752]

I understood the problem ... what confused me was the proposed solution.

But my previous question still remains. Is this site "big" enough to warrant a block in the EasyList .. or should a user just add a general whitelist for that subdomain. Like:

Code: Select all

@@http://dblp.mpi-inf.mpg.de/

?

[eighty5cacao]

My point was that the OP never proposed a solution - he only specified what filter was matching (i.e., blocking) the script in question. What probably confused you is that you did previously have that $domain parameter on that particular filter until you removed it to replace it with a whitelist string.

I am personally leaning toward marking this issue as "user" - but I am not very familiar with the site in question, and I don't really have time to look for Alexa stats right now. Since this is a German educational institution, is there anything that could be done in Ares' list about this?

I apologize if I have been unnecessarily rude or pushy. Go ahead and relax/take a break.

[rick752]

NP.

I'm leaning towards this as a user issue. I don't believe that the site qualifies as a 'big' site. If I had to find a way to fix every little thing on smaller sites, I would go crazy and the filters would be miles long.

I say the user should just whitelist that subdomain as suggested in my post above.

Thanx for you input though, eighty5cacao

[Ares2]

It seems that part of the rule in question got lost during this thread.

Code: Select all

/logging.js

should be

Code: Select all

/logging.js$domain=~banking.ing-diba.de

[rick752]

I think this is a user issue, Ares. I don't think that I should make exceptions for small sites.
I left this up to the user.

Also the $domain solution is the incorrect domain. That is not the domain I am ending up on there per the link. Are you being redirected to something else?

[Ares2]

OK, I guess you should read this thread again, eighty5cacao already tried to explain your misunderstanding to you.

The original rule before you started to read this thread was

Code: Select all

/logging.js$domain=~banking.ing-diba.de

(=blocks logging.js on all sites except for banking.ing-diba.de. This $domain exception was added here: http://forums.lanik.us/viewtopic.php?p=12481#p12481 )

In this thread here, the OP gave you a link to a different German site (mpg.de) where /logging.js$domain=~banking.ing-diba.de prevents the search feature from working correctly. For some reason, you assume(d) that this is a filter suggestion (and now wonder why it's a different domain) when in fact he just c&p the filter in effect that contains the domain exception for the other site.

Because of your misunderstanding, you've removed the old $domain exception and I asked you to fix this again in the last post.

I tried my best to explain it to you. Did you get it now?

[rick752]

Ah. It WAS my misunderstanding. I see that he was just showing me the EXISTING rule.

Do you think it is worth adding this domain to the rule .. or just leave it as a USER thing?

(I'm watching the Daytona 500 right now and I keep getting distracked)

[Ares2]

Just change

Code: Select all

/logging.js

to

Code: Select all

/logging.js$domain=~banking.ing-diba.de|~mpi-inf.mpg.de

and everybody is happy.

BTW, me goes to sleep now (only 7 hours left).

[rick752]

[quote="Ares2"]Just change

Code: Select all

/logging.js

to

Code: Select all

/logging.js$domain=~banking.ing-diba.de|~mpi-inf.mpg.de

and everybody is happy.

Okay .. done

[gst]

Hello,

Just change

Code: Select all

/logging.js

to

Code: Select all

/logging.js$domain=~banking.ing-diba.de|~mpi-inf.mpg.de

and everybody is happy.

Okay .. done

Sorry for respondy only now, but I somehow missed the topic reply notification.

Thanks for fixing this issue. Regarding the "publicity" of the site: DBLP (Digital Bibliography & Library Project) is one of the major search engines for academic computer science papers. So it is not that widely known (in general), but therefore important to many computer science academics.