My first published code in quite a long time, bmtu.
However, the public Twitter site isn’t really a permanent store for that information: it may disappear over night, they may have an horrific crash or, for perfectly reasonable performance reasons, they may expire or remove access to old tweets. In fact, you can only go about 3,200 posts back, so if you’re prolific, it may make sense to start backing up now.
Trevor pointed me at Tweet Nest, but it does a lot of things I don’t need (like analytics) and it uses an environment that I don’t run on my hosting (PHP, MySQL). The homepage is vocal about being tested in LAMP environments. I run Linux/Nginx/SQLite/Python – a LiNgSqPy stack. Catchy.
If you have PHP and MySQL hosting, or you don’t know what you have, you should probably stop here and just install Tweet Nest. If you have some ill-defined and lofty idea of software minimalism, but not so minimal that it doesn’t pull in a (smaller) SQL database engine, please check out the project’s Github page.
bmtu is designed to recover when it fails, and run periodically from a cron, where it will slavishly update an SQLite database in your home directory with the latest 140-character wisdom from any user (who doesn’t have a private timeline!) you give as a parameter. It uses 2+ anonymous API calls per hour, and comes with a README explaining its use. It’s licensed under an MIT-X11-style license.