API v1 Retirement is Complete - Use API v1.1 | Twitter Developers
Today, we are retiring API v1 and fully transitioning to API v1.1. Given the array of blackout tests, blog posts, 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. Based on the blackout tests and looking at the numbers, we can see that the vas
OAuth 2.0 App-Only (Bearer Token)
<g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2
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. On March 5, 2013 we held our first blackout test on the retiring API v1 to give you and other developers an opportunity to understand the impact that this aspect of the API's departure will have on your applications, websites, widgets, and services. The API responded t
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. We’ve brought back the Allow this application to use 'Sign in with Twitter' option. You
Planning for API v1’s Retirement | Twitter Developers
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. Who is affected? If you're a site owner that uses one of the older "goodie" widgets (e.g. profile, favorites, search and list widgets), you should move to Embedded Timelines as soon as possible. Likewise, if you'v
Moving to 64-bit Twitter User IDs | Twitter Developers
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. This
Calendar of API changes | Twitter Developers
This page lists important upcoming dates for consumers of Twitter's APIs. The dates listed will be as specific as possible, but may not be exact for various reasons. Please continue to follow @twitterapi and the Twitter developer blog for announcements about the platform. Upcoming changes Estimated date Description Announcement Affected APIs
How to embed Twitter timelines on your website | Twitter Developers
Today we’re bringing Twitter and the web closer together by launching new real-time tools for website developers. With our new embedded timelines you can place any public timeline on your website, connecting your readers with the Tweets that you and others create on Twitter. With one line of HTML you can deliver any account’s Tweets, favorites, a list, search query or #hashtag directly to your web
Current status: API v1.1 | Twitter Developers
Today, we're excited to release the next version of the Twitter API, version 1.1. A few weeks ago, we outlined many of the v1.1 changes, and with today's release, we've also updated the Developer Rules of the Road (see a summary of the most important policies here) and Developer Display Requirements. To learn about all of the changes, be sure to see the Overview of Version 1.1. You'll notice that
Changes coming in Version 1.1 of the Twitter API | Twitter Developers
At the end of June, I wrote about how we're working to deliver a consistent Twitter experience, and how we would soon introduce stricter guidelines about how the Twitter API is used. I'd like to give you more information about coming changes to the API and the migration plan while offering insights into today's Twitter ecosystem and why we're making these changes. In the coming weeks we will relea
API Housekeeping | Twitter Developers
When we originally released the Twitter API back in 2006, little thought was given to API design patterns like explicit versioning, subdomain partitioning, and response structures that would scale with the rapid but unexpected growth of the Twitter service and platform. Over the past two years we've continued refining and upgrading our original API and the monolithic infrastructure that powered it
Twemproxy: A fast, light-weight proxy for memcached | Twitter Developers
Twemproxy: A fast, light-weight proxy for memcached Today, we're open sourcing Twemproxy, a fast, light-weight proxy for the memcached protocol. Twemproxy was primarily developed to reduce open connections to our cache servers. At Twitter, we have thousands of front-end application servers, and we run multiple Unicorn instances on each one. Each instance establishes at least one connection to ever
Turning on gzip for stream.twitter.com this week | Twitter Developers
As previously announced, we are planning on turning on gzip compression for stream.twitter.com this week. A gzipped stream offers a huge bandwidth reduction over an uncompressed stream, so if you're consuming streaming data from stream.twitter.com, we encourage you to support this feature. For information on how to request a compressed stream, and for a workaround to an issue which Java clients ma
Say hello to Bootstrap 2.0 | Twitter Developers
Six months ago we open-sourced Twitter Bootstrap, an extensive front-end toolkit for developing web sites and applications. Woohoo! Twitter Bootstrap, an open-sourced CSS/HTML framework from myself and @fat, just went live: dev.twitter.com/blog/bootstrap… #kaboom— Mark Otto (@mdo) August 19, 2011 Since then, Bootstrap has grown to be one of the most popular projects on GitHub, the largest open sou
New Withheld Content Fields in API Responses | Twitter Developers
The Twitter REST API will soon return new data attributes to accommodate specific circumstances in which Twitter is required to withhold certain content in particular countries. We provide more detail on this on our Twitter blog and our Support pages. The new attributes, withheld_in_countries and withheld_scope, will denote which countries the Tweet or the account is being withheld in, as well as
Temporary Streaming API Outage | Twitter Developers
I received a 503 error when trying to connect to a Twitter keyword filtered stream. The error code says: 503 Service Overloaded. You shouldn't see this error on the streaming API. If you do contact API team. Engineers have identified the issue and are working to deploy a resolution to all affected stream clusters. 2011-01-04 5:45pm Pacific: We expect to be fully recovered in 1-2 hours. 2011-01-0
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
https://dev.twitter.com/blog/introducing-custom-timelines
https://dev.twitter.com/blog/application-only-authentication
https://dev.twitter.com/blog/timeline-api-announcements
Making API responses match the request Content-Type | Twitter Developers