You are right. This is an early version. Thanks for the feedback. I would have liked to post it to showhn on Monday when I had cleaned it up a bit but fate took it out of my hands.
I'd do that too but it would be cached and updated hourly. Why hit the Twitter api on each request?
You could set the app up to call the Twitter API but cache the response in memory or something like Redis so you don't need any background jobs/file management etc.
I've used memcached a lot but there's also benefits to caching a JavaScript file for an hour at a CDN and removing all load from that request.