Bad Behavior Behaving Badly
I’ve had to temporarily disable Bad Behavior; something about 1.2.1 didn’t like a number of my users. Now, it’s quite likely that the issues do fall on their end, but in the meantime, I’d rather field more comment spam and not inconvenience my users. Generally, I go for the solutions that inconvenience me less, but frankly, it’s more convenient for me to handle comment spam than it is for my users to be unable to reach their own Weblogs.
I’m sure something will work out soon and I’ll be back to being a happy BB user. 
Posted September 20th, 2005 in WordPress by Geof F. Morris.
[...] I’ve been extended an invitation here to WordPress.com, and I will use this as a space to post my thoughts and ideas about WordPress. I’ve been doing that on my Weblog for over a year now, but I’ll do it here—some entries may get posted to both locations, but I’ll try to avoid overlap in areas where it doesn’t matter. [For example, if I’m talking about WP and something else, it might end up in both places, or it might just stay over yonder.] [...]
September 20th, 2005 at 11:44BB >= 1.2 puts a “reason” in its log entry for every refusal. Of course, you have to go digging through the database to look at the logs, but once you have that reason, you should be able to feed that back to IOError and get him to do an update pretty quickly.
I would be really interested to know what it complained about. I admit that I’ve wondered how much BB overblocks… simply because tuning “signature-matching” tools like this can be really tricky. There are a LOT of user agents out there.
If you figure it out, let me know.
September 20th, 2005 at 17:13I did. It didn’t tell me much. The reason is automated; I wish I had a better paper trail, but that does cause additional overhead, and he’s trying to have BB be very light on the overhead.
September 22nd, 2005 at 15:28