Downloaded 38 times
![.NET & TwitterExpect-100 Continue (HttpWebRequest) Request.ServicePoint.Expect100Continue = false;302 Redirects if ( response.StatusCode == HttpStatusCode.Redirect ) { this.Url = new Uri( uri, response.Headers["Location"] ).ToString(); this.CookieContainer.Add( response.Cookies ); }64-bit IDs (ulong - Convert.ToUInt64(“”))LinqToTwitterhttp://www.codeplex.com/LinqToTwitterTweetsharphttp://code.google.com/p/tweetsharp/DotNetOpenAuthhttp://dotnetopenauth.net:8000/](https://image.slidesharecdn.com/twitterandoauth101tvug20091006-091013161011-phpapp02/75/Twitter-API-OAuth-101-TVUG-October-2009-14-2048.jpg)
![Downsides of HTTP Basic AuthBase64(byte[] “username:password”)Giving credentials away to third partiesPassword changeTrustRate limit by application IP](https://image.slidesharecdn.com/twitterandoauth101tvug20091006-091013161011-phpapp02/75/Twitter-API-OAuth-101-TVUG-October-2009-19-2048.jpg)
Uploaded byAndrew Badera
Twitter API & OAuth 101 TVUG October 2009
This document provides an overview of Twitter APIs and OAuth authentication. It discusses Twitter's growth statistics, available APIs for accessing timelines, search, and direct messages. It then covers OAuth and how it provides a more secure way to authorize applications compared to basic authentication. The document concludes with best practices for implementing OAuth and questions from the audience.
More Related Content
Similar to Twitter API & OAuth 101 TVUG October 2009
Twitter API & OAuth 101 TVUG October 2009
- 1. Twitter & OAuth101What’s this twit all about?Andy Badera (@andrewbadera)andrew@badera.ushttp://blog.badera.us/TVUG October 2009
- 2.
- 3. The Numbers79.7M usersas of October 4th (all inclusive; ~50M “official”)$153M in funding as of end of September28,000+ applications30,000+ developers$23M+ invested in third party app startups
- 4. Growth April 2008-2009ViaTechCrunch
- 5.
- 6. REST APIapi.twitter.comReturns: XML,JSON, RSS, ATOMRead timelinesSend tweetsRead/send Direct Messages
- 7. Search APIhttp://search.twitter.com/Returns: JSON,ATOMTrendsTerms (“from:andrewbadera”)Geolocation (“near:albany within:5miles”)
- 8. New StuffGeolocation (improved)GroupListsRetweet APIAddress BookApple PushSearch API cleanup
- 9.
- 10.
- 11.
- 12. What’s safe touse?Avoid “Twitter”Avoid bird graphicsAvoid similar UIBiz sez: “Use ‘tweet.’”
- 13. GoalsRegister a newOAuth applicationRetrieve timelinesSend TweetsSend/Receive Direct MessagesQuery Search API
- 14. .NET & TwitterExpect-100Continue (HttpWebRequest) Request.ServicePoint.Expect100Continue = false;302 Redirects if ( response.StatusCode == HttpStatusCode.Redirect ) { this.Url = new Uri( uri, response.Headers["Location"] ).ToString(); this.CookieContainer.Add( response.Cookies ); }64-bit IDs (ulong - Convert.ToUInt64(“”))LinqToTwitterhttp://www.codeplex.com/LinqToTwitterTweetsharphttp://code.google.com/p/tweetsharp/DotNetOpenAuthhttp://dotnetopenauth.net:8000/
- 15. RateLimitRatelimit: 150 RESTGETs/hourX-RateLimitX-RateLimit-RemainingX-RateLimitWhitelisted: 20000
- 16.
- 17. In the beginning,HTTP BasicHTTP Basic AuthorizationSimpleFamiliarAuthorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
- 18. Basic Auth Pullsa Fail Whale
- 19. Downsides of HTTPBasic AuthBase64(byte[] “username:password”)Giving credentials away to third partiesPassword changeTrustRate limit by application IP
- 20. O-wot?Secure API authorizationBlaineCook (Twitter)Chris Messina (Ma.gnolia)Currently: OAuth 1.0AOAuth.netShannon Whitley’s OAuthBase.cs
- 21. How OAuth WorksSharedsecretNonceTimestamp
- 22. OAuth & TwitterMovesburden of ratelimit to user accountRead/write (typical)Sign-in with Twitter“Guns for cash” – one time auth
- 23.
- 24.
- 25.
- 26.
- 27. TechnicalParameter sortingParameter URLencodingServer clock
- 28. SocialOAuth is nota panacea!Use common sense!
- 29. OAuth Best Practice“Aswith OpenID, OAuth is difficult to implement correctly and securely. Pick a good, dependable library to take a dependency on instead.” --Andrew ArnottDotNetOpenAuth Author via email
- 30. Q&AThanks for yourtime.Any questions?
- 31. Drinks!JJ Rafferty’sRoute 9Northof Latham Traffic Circle on rightNext to Price Chopper parking lotAcross from Red Robin
- 32. BibliographyAlex Payne slidesharepresentation: “Twitter API 2.0”, http://www.slideshare.net/al3x/twitter-api-20Mashable: “Twitter’s Value: 5 Eye-popping Stats”, http://mashable.com/2009/10/04/twitter-stats/Biz Stone blog entry: “May the Tweets Be With You” http://blog.twitter.com/2009/07/may-tweets-be-with-you.html
- 33. ResourcesTwitter API docshttp://apiwiki.twitter.com/Twitter Dev list http://groups.google.com/group/twitter-development-talkAPI blog http://apiblog.twitter.com/ (not well updated)@andrewbadera (http://twitter.com/andrewbadera)http://blog.badera.us/andrew@badera.us
Editor's Notes
- #2 Who’s heard of Twitter? Who has at least one account? Who’s been using it longer than a year? Who uses a third-party app like Tweetdeck?
- #3 Brainstorming event while Jack was at Odeo in 2006, started as internal service; really broke out at 2007 SXSW. Working name was “Status,” “twitch” was a suggested production name, but it wasn’t quite right for some people. Twitter was the word below it in the dictionary; “twttr” was the original form used, in the spirit of flickr & such. Jack Dorsey, Chairman, Former CEO, Founder, Evan Williams, CEO, Biz Stone, Creative Director. Union Square Ventures early and major backer. Other investors include
- #4 Some apps have already been acquired by Twitter or third parties for significant sums. (Tweetdeck by Seesmic, Summize by Twitter)
- #5 Well over 1 Billion tweets – the first tweet at or over a billion was written in late 2008 by a bot. Go figure. Over 5000 tweets/minute during Obama’s inauguration; now over 10,000-25,000/minute, or 250+ tweets/second. Hundreds of millions of requests served per day. Personally billing more in Twitter work alone in 2009 than I did in total independent consulting in 2008.
- #6 Three different APIs. Mention XMPP. Mention Starling – Ruby persistent queue using memcached, developed in-house. Backend now runs on Scala (over 2009). Interface still runs on Ruby on Rails. Will be focusing on REST and Search APIs tonight.
- #7 REST API can do everything a user can do, and more.
- #8 Recognizes trends, with and without # hashtag syntax. Allows viewing of historical trends, searches for keywords, updates to or from specific users. Started out as Summize, acquired by Twitter in mid-2008. Is not 100% uniform when compared to main REST API. Will migrate to api.twitter.com. In order to correlate a result from the Search API with an actual user, you need to do a lookup against the main API – painful cost when it comes to ratelimiting.
- #9 api.twitter.com is new. Twitter is also introducing API versioning. (ABOUT TIME!) New lat and long parameters, more accurate “near” searches. GeoRSS and GeoJSON. Address Book – allegedly “secure and spammer-hostile” method to find Twitter users given an email address.
- #10 Alex Payne, platform lead, second engineer hired (after Blaine Cook, former lead, former VP)RaffiKrikorian, platform engineer, Marcel Molina, translator & platform engineer and former Rails core team member, Ryan Sarver, platform engineer.
- #12 Twitter is “uncomfortable” use of the word “Tweet” (letter to unnamedapp developer.) MyTwitterButlerautofollow app -> MyPostButler. At least one other instance. Murky. Twitter unresponsive. Disappointing.
- #13 Biz’s blog entry latersays use “tweet,” and talks about the trademark filing. Too bad, they lost the April 16, 2009 trademark filing. Sam Johnston’s blog entry. Use “tweet,” use “post,” use “chat,” don’t use “Twitter.”
- #15 Twitter chokes on Expect headers – make sure to quash them! (Expect defines certain behavior expectations by client.) 302 spam countermeasure … #fail!
- #16 Response to all REST calls includes:X-RateLimit-Limit the current limit in effectX-RateLimit-Remaining the number of hits remaining before you are rate limitedX-RateLimit-Reset the time the current rate limiting period ends in epoch time.
- #17 Whitelisting: per account or per IP
- #18 Who here is familiar with HTTP Basic Authorization? What does it look like? **mention source param**
- #19 [Post update to Twitter using HTTP Basic Auth.] Well gee, that doesn’t seem that tough, and it works. So what’s wrong with it?
- #20 Putting password on the wire – encoded, not encrypted! SSL solves the problem, but not everyone is/was using https calls, and SSL can be expensive. Ratelimit: 150 REST GET/hour.
- #21 Not an authentication protocol per se, but is evolving into or being used as such. Mention 1.0 clickjacking issue. Mention PIN?
- #22 Shared secret – OAuth access token. Nonce value. Timestamp. Signature hash digest of all parameters, sorted lexicographically.
- #23 [Register new OAuth web app with Twitter. Walkthrough user approval process.]
- #24 [Retrieve public timeline. Retrieve individual timeline. Retrieve friends timeline.]
- #25 OK, pulling that information is nice, but I think what we’re probably all a little more interested in is the messaging aspect. [Send update. Send DM. Retrieve DMs.]
- #26 [Query search API; term, username, near, tags. Mention TweetHook?]