Robots crashed the server

Today there was some downtime as a rogue robot made too many connections to the database and caused it to stop responding. In the future we’ll build some more caching to be able to handle more concurrent connections but we’ll also build in robot banning code that will block robots that don’t respect the robots.txt protocol.

Right now the blog is on the same server, so it was down as well but in the future we’ll move the blog to a separate server so it can serve as a good place for updates when the main site is down.