I have no idea and their web site doesn't tell. I filed a bug report on this with them, but don't expect any response. It might be a HTTP header, or the fact that we follow all the bibtex links on the page.
Christiaan On 4 Jan 2008, at 10:57 PM, Adam R. Maxwell wrote: > Does anyone know how Google Scholar decides to block requests? I > used it for a search (6 pages @ 20 items/page), quit BD to add a > feature I needed, then when I relaunched and tried to use it again > I was greeted with this: > > // begin quote > We're sorry... > > ... but your query looks similar to automated requests from a > computer virus or spyware application. To protect our users, we > can't process your request right now. > > We'll restore your access as quickly as possible, so try again > soon. In the meantime, if you suspect that your computer or network > has been infected, you might want to run a virus checker or spyware > remover to make sure that your systems are free of viruses and > other spurious software. > > We apologize for the inconvenience, and hope we'll see you again on > Google. > // end quote > > They also blocked OmniWeb on the same machine, but at least OW > worked again after I entered the captcha. BD is still blocked even > after entering the captcha. I'm assuming it's because we make too > many URL requests in a short time, but I wonder if there's anything > we can do to prevent it? > > thanks, > adam ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
