I was doing my morning blog reading and I went to post on .eburke’s blog. I host eburke’s blog on the same installation of Movable Type that I use for my blog. Comment done.
So then I go over to my own blog to post a reply comment to someone and I received an error:
In an effort to curb malicious comment posting by abusive users, I’ve enabled a feature that requires a weblog commenter to wait a short amount of time before being able to post again. Please try to post your comment again in a short while. Thanks for your patience.
This is a new feature of a recent version of Movable Type called comment throttling. When someone tries to comment to many times to quickly, they get this error. Its basically a way to help slow down the spammers that hit my site constantly. Cool, but I am not a spammer!
After some digging through the source code, I figured it out. eburke’s blog runs in the Eastern timezone and mine in the Mountain timezone. So we are apart by 2 hours. After looking in the database I noticed that the time of the comment was 10 AM. I posted the comment at 8 AM MST. But it interpreted that as 10 AM since eburke’s blog is set to EST. Now when I try and comment to my own blog it thinks I should be banned because I already made a comment in the future. I won’t be able to make my next comment till its 10 AM MST + the throttling time.
I reported the bug to the Movable Type bug list. Hope they fix it.
So the moral of the story is that I figured out exactly what was wrong and I self-corrected it. Then I gave the information to the owners of the code and should they integrate it, another bug solved for the greater good…I guess.