Not Everyone Hates Twitter’s New API – And One Company Thinks It’s Pretty Neat

You’ve heard from developers a-plenty complaining about how unfair Twitter has been to them lately. And you’ve heard the doom and gloom about those being shut down due to Twitter’s pending API changes. Heck, we even started  an API Limit Death Watch to chronicle the gruesome details.

Imagine our surprise to come across a developer singing Twitter’s praises – and even after they’ve gone through the process of implementing the required API changes.

ThinkUp is a free, open source web application that captures all your activity on social networks like Twitter, Facebook, Google+ and Foursquare.

All you need to run ThinkUp is a web server that can run a PHP application – and the know-how to do that sort of stuff!

And if you DO know how, you’d probably really like ThinkUp. According to Gigaom, “[t]he dashboard shows the most retweeted content, the times of day when tweets get the most activity, the individual users who respond most, and provides all kinds of charts and graphs for presenting that information visually.”

And it has an open API, which is (at least partially) dependent on Twitter’s API. So it’s very fortune ThinkUp thinks so highly of the upgrade.

The API 1.1 changes affected ThinkUp in two major ways, and a few minor ones, which you can read in detail here, but here are some highlights:

Twitter’s new rate limits are generous, and across all the endpoints ThinkUp uses, they give the application more calls per hour than it had before. Twitter also enforces the 1.1 rate limits every 15 minutes instead of every 60, which means ThinkUp users can update their data more often without maxing out.

Second, API 1.1 required ThinkUp to move from consuming XML to JSON Twitter data. This transition was a long time in coming, and the 1.1 deadline was just the nudge we needed to make it happen. . . . Our new JSONDecoder classwraps PHP’s built-in procedural JSON functions in a smarter, object-oriented interface, and all the ThinkUp plugins that consume JSON can now use it to their advantage.

And the “new Twitter” necessitated additional beneficial changes to the visual layouts and helped them create “a simpler user interface.”

Have you successfully (and happily) made the transition to Twitter’s new API? Let us know! 

(Woman image from Shutterstock)