Twitter Platform Issue Tracker Deprecates Google Code Tracker

Twitter listening to the feedback, today launched "Twitter Platform Issue Tracker," a canonical place to host, track and report when issues are resolved.The new Issue Tracker deprecates the Google Code Tracker that the company was using.Twitter says "All Twitter API Issues are now listed on a dev.twitter.com dedicated page, which is directly accessible from the […]

Twitter listening to the feedback, today launched "Twitter Platform Issue Tracker," a canonical place to host, track and report when issues are resolved.

The new Issue Tracker deprecates the Google Code Tracker that the company was using.

Twitter says "All Twitter API Issues are now listed on a dev.twitter.com dedicated page, which is directly accessible from the API Health top-bar menu. Issues are organized by Status (Triage, In Progress, or Closed) and you can subscribe to each of these statuses, just like you'd do for discussion categories. For example, you might be interested in receiving an email notification each time an issue is closed."

“Note that we're not only highlighting active "hot" issues - but also recently closed issues - on the API Status page, so you can check the health of the Twitter Platform in one place," added Twitter.

Each API Issue has its own dedicated page, giving you all the details you'll need:

  • The Issue status, summary, description, latest updates, and an ETA (when we expect to have it solved)
  • Related Documentation pages (i.e. API Resources) that are impacted by this Issue
  • Related Discussion threads where you can discuss this particular Issue, get additional support, and share workarounds
  • A subscription option so you can receive email notifications each time a specific Issue is updated, and also voice your concern (we count, display and use the number of subscriptions as a metric to prioritize bug fixing efforts)

Twitter will also give developers a minimum is 30 days advance notice before 'sunsetting' anything. For more broad, sweeping changes, Twitter says it'll be flexible with developers and give them as much time as possible.

Rate limits are a big issue for Twitter developers and the company says that it permits 350 requests per user (oauth_token) per hour if you're making authenticated calls and 150 per hour against the calling IP address for unauthenticated calls.

The company notes, "Because we maintain edges between Issues, Documentation pages and Discussion threads, we can now display "warnings" on each API Resource affected by an active Issue. The idea with this warning is to prevent developers from losing time wondering why X,Y or Z isn't working as expected."

Twitter also said that it is committed to push Site Streams, which will allow apps to receive real-time updates for events such as mentions, follows, timelines, and more, out of beta by Q1 of 2011.

Twitter promises to be more communicative overall with developers and especially help third-party developers work through authentication issues using oAuth.

More Info: Twitter Platform Issue Tracker