Twitter API 1.1 Adventures
On June 11th, Twitter decided to close the API v1 and start using the new V1.1. So far, so good…a new version of an API, new features, what could go wrong?
How can I, a humble adventurer, keep developing the site statically and still fetch the latests tweets?
Unix (or in this case Linux) is the answer. My idea was to create a cron that fetch the latests tweets every X minutes, and write the result in a file accesible by the server (in my example latest_tweets.json). Then I get the information from this file using ajax and voilá!
Thanks to a post I found on the twitter forum I can write the script in no time.
But Fear not the new twitter API! If you are also an adventurer trapped in this very same situation, you can take a look at my script and use it to walk in the forest of the REST without fear.