September 18, 2014
Single purpose API
Related Articles (724)
At YourTrove, a lot of what we do involves ingesting social content via APIs and then regularizing that data within our system. For a lot of data, this is pretty straightforward. For example, while Facebook and Flickr might return different meta data, or name fields differently, no one disagrees that a photo is a photo. This is true for essentially all uploaded binary user generated content.
What does a tool maker do when his tool breaks? He builds a new tool to patch the broken one. At least that is what David Beckemeyer (Mr Blog) did when his tweeting garage door opener was threatened by the approaching OAuthpocalypse. This date with destiny for all Twitter programmers is the planned June 30th cutoff of basic authentication. At that point all Twitter apps must communicate with the API through OAuth authentication instead of the much less complicated user name/password form of HTTP Authentication. There are many good reasons for this change, which have been repeated endlessly on the Twitter developer forum, but in practice it is a lot of added complexity, more complexity than David wanted to build into his little, simple garage door device.