We’re proactively making room for more lists on Twitter by expanding their IDs to 64-bit integers. If you’re using our REST and Streaming APIs, you should confirm that your database, server-side and client-side code consume the safe string-based identifiers represented in “id_str” fields instead of the integer-based identifiers found in the “id” field of Twitter List objects and related references.
If you use our streaming APIs, you should be aware of a change that’s coming in a couple months: We are updating the SSL certificates for userstream.twitter.com and stream.twitter.com on November 4, 2013.
For a variety of reasons, the numbers used to identify accounts via Twitter’s API grow faster than the actual number of accounts in the system. Currently, user IDs fit in 32 bits—a standard size for integers on many platforms. In January, we explained that the current pace of Twitter user ID allocation meant that we’d exceed 32 bits sometime this year. All developers should make sure their code will handle the switch.
Hundreds of thousands of websites and publishers embed Tweets to share the best of Twitter with their readers. From world news, to sports, politics and entertainment, Tweets have changed the way breaking news is covered. And they help people everywhere discover important Tweets, even outside of Twitter.
Today, we are retiring API v1 and fully transitioning to API v1.1. Given the array of blackout tests, blogposts, Tweets and other updates, this should (hopefully) not be a surprise. Before I get into the slew of resources available for you, let me first say thank you for your cooperation over the last several months.
Today, we’re introducing 11 new Twitter Certified Products. Since we introduced the program last summer, our goal has been to help businesses find tools and services that make them more successful on Twitter. To date, Certified Products have been largely U.S.-focused; this new group includes companies from Europe, Japan and Latin America –– extending the program’s global footprint and empowering brands and publishers around the world.
To build stable, robust applications, you need to understand when, why, and under what conditions your apps may crash. On the Android platform, variations in hardware, along with the multitude of in-market OS variants running your apps, make it even harder to identify and resolve crashes.