In further preparation for the retirement of API v1 on June 11, 2013, we'll be conducting another blackout test on May 22nd, 2013 from approximately 20:00 UTC to 21:00 UTC (1pm to 2pm Pacific).
During the blackout test, API v1 will respond to authenticated & unauthenticated requests with "HTTP 410 Gone". Please read this post for a more complete accounting of what to expect.
Engineers here at Twitter are always looking for ways to increase efficiency and simplify our codebase. To that end, we're deprecating HTTP 1.0 support for all streaming API endpoints. While our streaming API continues to grow, this version of the protocol is rarely used. Also, its successor (HTTP 1.1, introduced in 1999) offers features that are useful for streamed responses.
We're extending the API v1 retirement date from May 7, 2013 to June 11, 2013, in order to accommodate additional blackout testing.
The first few months of 2013 brought a number of changes to the Twitter platform. In case you haven't kept up with our recent announcements, here are some key highlights.
The Retirement of API v1
Several major milestones relating to the deprecation of API v1, which was announced last fall, have occurred during the first quarter of 2013.
When the Tweet button was introduced in 2010, Microsoft’s Internet Explorer 6 was our baseline. Now, most users have upgraded and we see IE6 usage dwindled. On May 13th 2013, we’re going to prune our support for that browser and its successor, IE7.
Twitter auto-links financial symbols (which look like $FOO) in Tweet text. These parsed symbols will soon be made available via the API under the Tweet "entities" object. Sections of text which match a dollar sign ($) followed by a word identifier will show up under the "entities/symbols" key. For example:
Twitter Cards are being used by more than 10,000 developers, mobile apps and websites to richly represent content on Twitter, including article summaries, user-posted photos, videos, songs, and more. Today, through those Cards, we're introducing a new way to bring people directly to your app from a Tweet, and we're adding new types of Cards, so you can more creatively show your content on Twitter.
We will hold another blackout test on April 16, 2013 beginning at 23:00 UTC (4:00pm PDT). Depending on the results of that blackout test, we may announce an additional test before the final retirement date.
There's a lot to keep track of in this migration. Here's a recap:
We're working on new Twitter platform features that we'd like to share with you at an upcoming mobile-focused event. If you’re a developer, product manager, designer, etc., working on a product with a mobile presence, then please join us at Twitter HQ on the evening of April 2nd, from 6:30pm to 9pm.
The content will cover how you can best integrate Twitter into your mobile experience. We’ll have limited space, so please register to attend:
Our Site Streams feed was introduced as a limited beta in August 2010. It is a powerful service which allows an application to read a stream of Tweets and social events for a set of authenticating users. With the inclusion of an optional with=followings parameter, Tweets and social events from all the users the connected user is following are also streamed.