Why should you care? Well, for one thing – the 1.0 API was starting to break and not get repaired in places. For example, you might have noticed that Social was no longer reliably finding tweets that referenced your posts by URL. This was due to a breakage in Twitter’s 1.0 search API. However, it works fine in the 1.1 API – now that is “fixed”. Yay!
So we’re pleased to be on Twitter’s 1.1 API, and the great folks at MailChimp have made some additional changes to the Social Proxy to make it easier for us to maintain Twitter API compatibility going forward.
We also threw in a couple of little bug fixes, check out the changelog in the README for details.
This post is part of the project: Social. View the project timeline for more context on this post.