We keep seeing that error, and are guessing it has to do with the Twitter API. We need to create some better error handling. Thanks for sharing.

By the way, just refresh a couple of times and you should see your results.