[ic] Bad Robot 24 hour wait not doing it's job

[Paul Jordan]

NOTE: Are people still aware the search is still down on the devgroup?

I get a literal TON of this:

64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/card/ 
WARNING: POSSIBLE BAD ROBOT.  accesses with no 30 second pause.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/card/ 
WARNING: POSSIBLE BAD ROBOT.  accesses with no 30 second pause.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/card/ Too 
many IDs, 24 hour wait enforced.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/pages/ 
WARNING: POSSIBLE BAD ROBOT.  accesses with no 30 second pause.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/pages/ 
WARNING: POSSIBLE BAD ROBOT.  accesses with no 30 second pause.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/pages/ 
Too many IDs, 24 hour wait enforced.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/card/ 
WARNING: POSSIBLE BAD ROBOT.  accesses with no 30 second pause.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/card/ 
WARNING: POSSIBLE BAD ROBOT.  accesses with no 30 second pause.
64.37.231.138 - - [01/December/2010:18:26:32 +0000] XXXXXXXXXXXXXX/card/ Too 
many IDs, 24 hour wait enforced.

Notice it says it's going to enforce a 24 hour wait, but that same IP keeps 
at it. I've been informed that the Robots stuff isn't a very thorough 
defense for these.

My question to everyone is what are you guys doing to block this traffic? 
There are repeatedly tons of these, and to me it's just stolen bandwidth and 
CPU cycles. Am I missing some standard everyone else is aware of, or is 
there any simple and creative ways to block these?

Thank you

Paul