Okay, so I'm unblocked. I couldn't tell you precisely how long it took - I was afraid to check too often. For me, it was in the neighborhood of 10 - 20 mins. That's a lot shorter than I deserved for the volume of unnecessary duplicate hits that transpired as a result of my laziness.
Props to the Base team for not making my penalty unmanageable. I'm getting back on testing but I promise to limit my tests to under 100 hits before stopping and re-tweaking. And I've tweaked my throttler to only allow 4 requests per second. A note for understanding: I am making so many reuqests since I divide the continent and approximately 1,600 sections (by northwest and southeast corner lat/lng points), then I loop through each, making up to 4 calls of 250 results each to get to the 1,000 limit mark. To top this off, this all rests inside another loop, which switches some other parameters out per loop. So, a full run of this script will make somewhere between 3,200 and 12,800 calls. - Nick On May 20, 12:56 pm, Nick Owens <[email protected]> wrote: > Ok, I admit it. I got greedy and was reckless w/ the Google servers. > I was testing a new application and I kept re-starting it to tweak > different parameters. I probably made some 40,000 requests in the > last few hours. So now my queries are blocked. The following message > tells me this: > > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > 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. > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > I was absolutely being careless and I'd like to apologize and start > the slate clean. I am sorry and I will be more careful next time, > doing only a few requests at a time, analyzing the results, and > tweaking parameters as necessary. I have learned my lesson. > > My question is: "Now what?" I mean, do I just wait for Google to > unblock my IP address from this type of similar query? Do I re-format > the parameters a bit by shifting them around? (actually I already > tried this and they're not stupid enough to block requests just by the > order of parameters) if I wait, how long should I wait? I understand > if I need to be penalized since I was acting w/ such reckless abandon > against their servers. I'd just like to know what the penalty is so I > can suck it up and plan to do something else for the next 12 hours, 24 > hours, 2 days, etc? > > I understand the difficulty in letting information like this out since > someone could plan on catching this exception and throttling their > requests around this penalty window. But I'm not one of those > companies! Whether it's email, API access, or anything else, > legitimate companies are always having to pay the toll for unsavory > companies who are trying to take advantage. I'm not talking about the > waiting penalty - I deserve that. I'm talking about not being able to > plan the final test phase of this project on any type of timeline > since I have no idea how long to wait. > > I wish there were someone to talk to - to apologie profusely enough > until I am forgiven. > > Not that it detracts in any way from my poor behavior but from what I > read before I started, the only limitation enforced by the Google Base > query API was 5 hits per second. This is apparently not the case, or > perhaps this limitation is calculated by rounding to the nearest > second. I throttle my requests so there's never more than 5 in a > single second but I measure out to the millisecond, so it's quite > possible my sixth request is after only 1.00001 seconds. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
