We just made some changes to our OAuth 1.0A flow, enabling applications to better control automatic redirection behavior in the "Sign in with Twitter" flow. With these changes, we recommend you log in to dev.twitter.com and review the applications you’ve created and the specific OAuth options available to them.
Today we’re releasing Hosebird Client, a Java-based client for Twitter's Streaming APIs. While Twitter has open-sourced a considerable amount of software, this is the first API client library we've developed in-house and are releasing to the world.
We’ll soon be adding new fields to Tweet structures returned by the API, helping developers more easily work with targeted subsets of Tweet collections.
You may know that a couple weeks ago, Twitter acquired Crashlytics, a mobile crash reporting solution. Today, we thought mobile developers would like to know that Crashlytics is folding its Enterprise features into its main product. This means that developers can now use Crashlytics with no usage costs or limits.
Here at Twitter, we love using Crashlytics for mobile crash reporting, and we think that you will too. You can read more about their announcement on their blog.
Back in September, we released the Twitter REST API v1.1 and announced that API v1 would be retired in March 2013. I'd like to provide you with more detail on the plan to retire API v1.
Every entity represented in Twitter's API has an ID associated with it. As we allocate larger and larger numbers for these IDs, the space required to store them must grow in turn. For example, we migrated Tweet IDs from 32-bit to 64-bit integers back in 2009, then did the same for direct message IDs in 2011. We expect to start allocating user IDs in a 64-bit integer space sometime this year.
Last summer we launched the Twitter Certified Products Program (TCPP) to help businesses find the tools they need to use Twitter more effectively, and to guide developers toward valuable opportunities.
Today, we’re expanding the program by adding nine members that address challenges we continue to hear often from publishers and brands, particularly around engagement and analytics. The primary reasons we’re working with these partners are:
We’d like to share some upcoming changes to our t.co link wrapper with the ecosystem. We’re going to be extending the maximum length of t.co wrapped links from 20 to 22 characters for non-https URLs, and 21 to 23 characters for https URLs.
To give everyone enough time to update their applications, this change won’t go into effect for two months - so please consider this a heads up. On February 6th, 2013, the GET help/configuration method will start to return the updated values for the length of characters returned in the following key-value pairs:
A few weeks ago in mid-November, our friends at Urban Dictionary decided to implement the Follow Button across their site. They were looking to integrate more with Twitter, and were curious to see how this small change might affect their follower count. At the time, @urbandictionary was seeing an average follower growth rate of 87 follows a day in the weeks leading up to their implementation of the Follow Button.
