A Recap of the First Quarter of 2013

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.

Deprecating IE6 and IE7 support in Twitter for Websites (TFW)

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 o

Symbols entities for Tweets

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 "<a href="https://dev.twitter.com/docs/platf

Mobile app deep-linking and new Cards

Twitter Cards are being used by more than 10,000 developers, mobile apps and websites to richly represent content on Twitter, including article summarie

A Special Platform Event | Twitter Developers

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.

Changes to following caps and message ordering for Site and User Streams | Twitter Developers

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.

API v1 Retirement Update: Blackout Tests, OEmbed, & Streaming API edition | Twitter Developers

Now that application-only authentication is released, we wanted to give you an update on the ongoing gradual retirement of API v1.

Do applications dream of authenticated requests? | Twitter Developers

People - our users - are central to everything at Twitter. Users read, retweet, favorite, and compose tweets. They follow other users and search for what's meaningful to them. The user is the primary agent of the Twitter experience, in all its varieties.

Changes to the 'Sign in with Twitter' flow | Twitter Developers

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.

The Hosebird Client streaming library | Twitter Developers

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.