Spammers exploit open systems so badly we end up suspending tens of thousands of blog every week, and unfortunately sometimes we screw up like above. I think what happened was probably caused by the bug, but when someone re-reviewed your account the “SEO” post stood out and raised a mental red flag.

Simple information that should have given you the benefit of the doubt, like the fact you were a paying customer, weren’t easily accessible to support folks. Since then we’ve cleaned up our processes and completely changed how the suspension system works so a f-up like above should never happen again, but if you have any problems in the future feel free to email me directly.

A) We’re expecting spikey traffic to the blog and don’t want it to effect our app performance. Once we have some interesting data with RescueTime, I think we can post things that will perform well on Digg, Delicious, Reddit, etc.

B) Our App is Rails and we don’t necessarily want to support PHP on the same server.

C) We don’t want to be dorking with WordPress upgrades/patches/security/etc. Presumably Matt and Co. at WordPress are better at that than we are.

Of course, all of this could be dodged by spending more money (spinning up a second server, having more dev-hours to fiddle with such things), but we’re a bootstrapped outfit.

But yeah, they’re a bit nuke happy with the suspend account button — which worries me since they’re making a play for being a major openid provider.