
API - Examples - Twitter
Get flash to fully experience Pearltrees
How to measure Twitter
Twitter API Ditches XML For Trends: New Features Are JSON-Only
The Twitter API is one of the widely used APIs in our directory. It is also one of the fastest changing, with updates going out to its developer list on what feels like a weekly basis. Some recent changes are especially big and mean an end to the GeoAPI , which Twitter acquired a year ago .
Twitter API Updates Mean an End to GeoAPI
When Twitter bought Mixer Labs in December, 2009, it inherited the startup’s then-recently launched GeoAPI , which offered a platform for building geo apps. The GeoAPI combined a places database of 16 million businesses with a reverse-geo-coder and support for geo-coded Tweets, Flickr photos, and even an iPhone SDK. Twitter kept the GeoAPI going after the acquisition—but that ends at the end of March. According to a developer who used to build his product on the GeoAPI, Twitter is shutting it down for outside developers. It is too much of a hassle to maintain, apparently. Twitter will still use it internally for its own apps.
Twitter Will Shut Off GeoAPI To Developers
As expected since Twitter photos was announced in June, the microblogging company has activated photo-tweeting from the Twitter API . With it, any application will be able to upload an image to Twitter’s servers as part of a tweet. Adding images via the API follows Twitter’s recent inclusion of the service for all users on its flagship website. Official Twitter-hosted photos have been readable in tweets since shortly after the announcement, though only a small number of users could post them. As we wrote in June, a “type” field, which currently is only photos, suggests video may be on the way. Techcrunch also notes that the call to statuses/update_with_media may also suggest additional types of media, or may simply be an attempt to future-proof the API.
Photo Upload Added to Twitter API
Fun With the Twitter API: No Programming Required: Online Collaboration «
Doc Searls Weblog · Twitter failings
Before that, the computer had been asleep all night. When I’ve seen this before, I thought perhaps Twitter in my browser had been hitting the API too hard for updates or something. But I didn’t even have my browser open. Neither my computer nor I had been doing anything with Twitter — as far as I know. This story says, “Twitter restricts the amount you can access the service to a set rate in an effort to prevent apps from mercilessly pinging Twitter every x number of seconds.”API - Examples - Twitter - Retweets
API - Examples - Twitter - TweetSentiments
API - Examples - Twitter - Annotations
OAuth-only Twitter: What it Means for JavaScript Apps
In a case like this, you’d want to implement most of this logic server-side, where you can keep the hard-coded credentials securely. You could potentially use Javascript to speak to your own servers to hustle the process along. Yes, this change will lead to better security because important information never leaves the server. It also has the effect of reducing the number of options for creating a JavaScript app. However, those using the search API with JavaScript will be unaffected, as it does not require authentication. Developers have had plenty of warning.OAuth is a great way to sidestep the dilemma of having to hand over passwords to third-party sites and apps to access user data. This is the primary reason the authentication method is fast becoming a de riguer part of today’s social APIs. But while OAuth solves one problem, it creates another — it greatly raises the complexity of simple apps. We’ve looked at the issue in the past , particularly with regard to Twitter’s transition to OAuth, which broke countless small scripts.
Connect to Twitter Without OAuth
Twitter has ended beta testing of the User Streams and portion of its Twitter Streaming API and brought it into regular production. While we've seen some clients take advantage of the User Streams, such as TweetDeck , the real-time Web is about to get a lot more real-time. Previously, third-party Twitter clients had a limited number of times they could request updates from Twitter, which meant there was a lag between when someone posted an update and you saw it in your client.

