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.
The Twitter REST API v1 will officially retire on Tuesday, May 7, 2013.
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.
Now that application-only authentication is released, we wanted to give you an update on the ongoing gradual retirement of API v1.
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.
Applications built on the Twitter REST API are typically vehicles for user interaction with Twitter, but we recognize that applications may sometimes need to interact with Twitter on their own behalf, without bearing a user context.
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.
