PageRenderTime 118ms CodeModel.GetById 43ms RepoModel.GetById 1ms app.codeStats 0ms

/projecte eclipse/TI/data/2012-documentos/76/2012-76-067.html
HTML | 406 lines | 391 code | 11 blank | 4 comment | 0 complexity | 7d0a723e09a31a4784a78ec22ef4021e MD5 | raw file
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">
  2. <html xmlns="" dir="ltr" lang="en-US">
  3. <head profile="">
  4. <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  5. <title>Twitter API Tutorial: Hello Twitter OAuth with PHP</title>
  6. <meta name="robots" content="noodp, noydir" />
  7. <meta name="description" content="This is the simplest possible path to using Twitter OAuth with PHP. It&#8217;s not that mysterious once you have all the steps in one place." />
  8. <link rel="stylesheet" href="" type="text/css" media="screen, projection" />
  9. <link rel="stylesheet" href="" type="text/css" media="screen, projection" />
  10. <!--[if lte IE 8]><link rel="stylesheet" href="" type="text/css" media="screen, projection" /><![endif]-->
  11. <link rel="stylesheet" href="" type="text/css" media="screen, projection" />
  12. <link rel="canonical" href="" />
  13. <link rel="alternate" type="application/rss+xml" title="140dev RSS Feed" href="" />
  14. <link rel="pingback" href="" />
  15. <link rel="EditURI" type="application/rsd+xml" title="RSD" href="" />
  16. <link href="/blog_images/140dev_logo_favicon.jpg" rel="shortcut icon">
  17. <script type="text/javascript" src="">
  18. </script>
  19. <script type="text/javascript" src="">
  20. </script>
  21. <script type="text/javascript" src="/wordpress/js/blog.js">
  22. </script>
  23. <script type="text/javascript" src="">
  24. </script>
  25. <script src="" type="text/javascript">
  26. </script></head>
  27. <body class="custom hello-twitter-oauth-php">
  28. <div id="container">
  29. <div id="page">
  30. <div style="padding-left: 1.1em;">
  31. <p style="float:left;"><a href="/" alt="Homepage of 140dev Twitter API Consulting" title="Homepage of 140dev Twitter API Consulting"><img style="margin-right: 4px; margin-bottom: 4px;" src="/blog_images/140dev_logo_icon.jpg"><img src="/blog_images/140dev_logo.png" /></a></p>
  32. <p style="float:right;width: 288px;text-align: right;color:#555;font-size:12px;margin-right:11px;">
  33. <span><b>Adam Green</b></span><br/>
  34. <span>Twitter API Consultant</span><br/>
  35. <a href=""><span></span></a><br/>
  36. <span>781-879-2960</span><br/>
  37. <a href=""><span>@140dev</span></a>
  38. </p>
  39. </div> <div id="header">
  40. <form method="get" class="search_form" action="">
  41. <p>
  42. <input class="text_input" type="text" value="To search, type and hit enter" name="s" id="s" onfocus="if (this.value == 'To search, type and hit enter') {this.value = '';}" onblur="if (this.value == '') {this.value = 'To search, type and hit enter';}" />
  43. <input type="hidden" id="searchsubmit" value="Search" />
  44. </p>
  45. </form>
  46. <p id="logo"><a href="">140dev</a></p>
  47. <p id="tagline">Twitter API Programming Tips, Tutorials, Source Code Libraries and Consulting by Adam Green</p>
  48. <div style="font-size:0px;height:8px;line-height:8px;border-bottom:3px solid #888;"></div> </div>
  49. <ul class="menu">
  50. <li class="tab tab-home"><a href="">Blog</a></li>
  51. <li class="tab tab-1 current-parent"><a href"" title="Twitter API Programming Tutorials">Tutorials</a></li>
  52. <li class="tab tab-2"><a href="" title="140dev Twitter Framework">Free Source Code</a></li>
  53. <li class="tab tab-3"><a href="" title="Hire Adam Green for Twitter API Consulting">Consulting</a></li>
  54. <li class="tab tab-4"><a href="" title="Adam Green’s Resume">Adam Green&#8217;s Resume</a></li>
  55. </ul>
  56. <div class="sidebar_tweetbox tweetbox">
  57. <textarea id="tweet_text">Tweet or Search here...</textarea>
  58. <div id="tweet_text_actions" style="display: none;">
  59. <a id="search_button" href="#" style="float: left;margin-left: 8px;">
  60. <img border="0" src="/blog_images/search-button.gif" style="margin-bottom: -6px; border: 0px none;">
  61. </a>
  62. <span id="tweet_length">140</span>
  63. <a id="tweet_button" target="_blank" href=",140elect,2012twit,140townhall,4more&amp;text=.%40140elect%20">
  64. <img border="0" src="/blog_images/tweet.png" style="margin-bottom: -6px; border: 0px none;">
  65. </a>
  66. </div>
  67. </div> <div id="content_box">
  68. <div id="content">
  69. <div class="post_box top" id="post-941">
  70. <div class="headline_area">
  71. <h1>Twitter API Tutorial: Hello Twitter OAuth with PHP</h1>
  72. </div>
  73. <div class="format_text">
  74. <p><em>All of the files mentioned in this tutorial are available as a <a href="">downloadable zip file</a>.</em></p>
  75. <p>New <strong>Twitter API developers</strong> approach <strong>OAuth</strong> with a great deal of fear, but it really isn&#8217;t that bad, especially if all you need to do is have a server based application communicate directly with the Twitter API. I think the real problem is the way Twitter HQ tries to <a href="">explain OAuth</a>, especially this amazing diagram:</p>
  76. <p><img src="" border="1"></p>
  77. <p><strong>Twitter OAuth programming</strong> doesn&#8217;t have to be anywhere near this complex. This tutorial will take you through all the steps you need to follow for any <strong>PHP application</strong> that has to send API requests directly from a Web server on behalf of a single Twitter account. This includes things like tweeting, following, list management, and practically all of the API calls. It&#8217;s true that building a full Twitter client that represents many users is more complex, although nothing as frightful as the diagram above, but one server talking to Twitter about one account is easy. </p>
  78. <h2>Registering a new application</h2>
  79. <p>You need to create an application before you can communicate with the Twitter API through OAuth. The great thing is that there is no approval process for Twitter applications. You just fill out a simple online form and your application is created. Here are the steps you follow:
  80. <ol>
  81. <li>Log into the Twitter account that your application will be working with. This is the Twitter account that will receive tweets, automated follows or any other changes through the API. Even if you just want to extract data about other users without altering this account, you must use an application tied to a valid Twitter account. For this tutorial I&#8217;ll register an app for the account @140devdemo, which I use for API programming tests. </li>
  82. <li>Go to the Twitter developer site at <a href=""></a>.
  83. <p><img src="" border="1"></p>
  84. </li>
  85. <li>Click the link to register an application.
  86. </li>
  87. <li>You will see a form that lets you describe the app.
  88. <p><img src="" border="1"></p>
  89. <p>For an application that uses a server script to connect to a single Twitter account you only need to fill out a few of these fields:
  90. <ul>
  91. <li>First give the application a name. If you are going to be tweeting through this app, the name is very important, since it will appear as the source of every tweet. You&#8217;ve seen this before for tweets sent by clients like Tweetdeck.</li>
  92. <li>The description field must also be filled out. What you enter here isn&#8217;t that important for this type of app. This message appears when someone gives approval for this app to access their account from a Web page. We aren&#8217;t writing that type of app here, so enter any kind of descriptive message you want. </li>
  93. <li>The application website field is used along with the name to create the source link on each tweet created by this app. This is a valuable form of promotion, because when you send a tweet through this app anyone who sees it can click the source link to visit your site. </li>
  94. <li>You can leave the organization field blank, leave the application field set to its default value of Browser, and leave the callback URL field blank. </li>
  95. <li>You should set the default access type field to read &#038; write. That will give your app the greatest flexibility.</li>
  96. <li>The application icon isn&#8217;t needed, again because nobody will be signing up with this app through the Web.
  97. <li>Then you just have to fill in the captcha, and click the register button.</li>
  98. </ul>
  99. <li>After a short delay, very short for anyone who has tried getting an app approved for the iPhone or Facebook, you will be presented with an information page for this app. There are some important pieces of data we need from this page. </li>
  100. </ol>
  101. <h2>Collecting your OAuth keys</h2>
  102. <p>An OAuth connection requires four key values called tokens and secrets. The application is identified by a token and a secret, and each user it represents also has a token and secret. I&#8217;m not going to go into the theory behind all of these values. If you wanted a bunch of theory, you wouldn&#8217;t be reading this tutorial, would you? And frankly, I don&#8217;t want to understand the theory myself. I do know that you must tell the Twitter API, &#8220;I am this app, acting on behalf of this user,&#8221; and these four values let you do that. </p>
  103. <p>Each application created for Twitter is automatically assigned these four values, and all you have to do is copy them from the right pages, and paste them into your script in the right places. To preserve an air of mystery, Twitter spreads out the values between two pages, because putting them in one place would make it too easy. Also, just to add even more confusion, the names of these four values tend to change randomly in different parts of the docs and interface. So follow very, very closely. </p>
  104. <p>First we get the consumer OAuth values. These represent the Twitter account that is being changed by your Twitter API calls. Since you registered your app while logged in to this account, Twitter automatically gives you its values. The trick is finding them. </p>
  105. <p>I registered this test app for the @140devdemo account, so I can find the values on the application&#8217;s OAuth Settings page. This page appears immediately after the app is registered. You can always get back to this page by going to <a href=""></a> while logged into the app&#8217;s Twitter account, clicking the link for Your Apps on the top menu, and then clicking the name of the application. Look for the part of the page that looks like this:</p>
  106. <p><img src="" border="1"></p>
  107. <p>I&#8217;ve blacked out part of these values for secrecy. You should never share your account&#8217;s OAuth values, because then people could do nasty things to you. Copy these values and put them in a safe place. Make sure you write down which is the key and which is the secret.</p>
  108. <p>Next we have to get the application&#8217;s OAuth values. To find these we look for the following set of links on the top right of this OAuth Settings page:</p>
  109. <p><img src="" border="1"></p>
  110. <p>Clicking the link for My Access Token will reveal the next two values we need:</p>
  111. <p><img src="" border="1"></p>
  112. <p>Again, I&#8217;ve blacked out part of them. These should also be copied and saved. Believe me, it gets a lot easier now. But let me take a short digression. I once had a great science teacher in high school who always said that when you read a book that is very confusing it is because the author was confused. I have to believe the Twitter people who designed their OAuth system were confused. There is no reason this whole process must be so byzantine. You have to laugh when contrasting it with the original conception of Twitter itself. Anyway, now we can move on to some programming, which is why you came here in the first place. </p>
  113. <h2>Getting a Twitter OAuth library</h2>
  114. <p>There are several good <a href="">PHP libraries for OAuth</a>, but if you are just starting out, I recommend the one by <a href="">Matt Harris</a>. I&#8217;ve also used Abraham Williams&#8217; library, but it is more of a wrapper for the entire Twitter API. If all you want is a library that makes the OAuth connection for you, and then gets out of your way, start with Matt&#8217;s. It&#8217;s what I use in my own code. </p>
  115. <p>All you have to do is <a href="">download</a> the compressed files, extract them, and upload them to your server. Then you can include or require the single library script, and create a connection by passing in the OAuth values. Calling the Twitter API with this connection means pulling out the right details from the Twitter API docs, which is much simpler than wrestling with the OAuth docs. </p>
  116. <h2>Decoding the Twitter API docs</h2>
  117. <p>We&#8217;ll be posting tweets as the example for this tutorial, so let&#8217;s move to the <a href="">Twitter docs</a> for this function. API calls are REST URLs, and there is only one portion of the URL we need. </p>
  118. <p><img src="" border="1"></p>
  119. <p>The version is always 1, at least until version 2 of the Twitter API appears, and the format is set to JSON by default in Matt&#8217;s library. Twitter HQ has made it very clear that XML is being phased out in favor of JSON throughout the API. So all we need is the specific part of the API call that applies to tweeting. In this case it is &#8220;statuses/update&#8221;. </p>
  120. <p>Next we need the request type, which is either GET or POST. In this case it is POST. </p>
  121. <p><img src="" border="1"></p>
  122. <p>Finally, we have to find the parameter names for this API call. These are passed with their values to the OAuth connection in an array. The parameter for the tweet text is &#8220;status&#8221;. </p>
  123. <p><img src="" border="1"></p>
  124. <h2>Simple tweeting script</h2>
  125. <p>At last we can write a script to <strong>post tweets through OAuth</strong>. I&#8217;ve written it as a function, <code>post_tweet()</code>, so you can include this script, and call the function in your own code. </p>
  126. <table><tr><td class="line_numbers"><pre>1
  127. 2
  128. 3
  129. 4
  130. 5
  131. 6
  132. 7
  133. 8
  134. 9
  135. 10
  136. 11
  137. 12
  138. 13
  139. 14
  140. 15
  141. 16
  142. 17
  143. 18
  144. 19
  145. 20
  146. 21
  147. 22
  148. 23
  149. 24
  150. 25
  151. 26
  152. 27
  153. 28
  154. 29
  155. 30
  156. 31
  157. 32
  158. 33
  159. 34
  160. 35
  161. 36
  162. 37
  163. 38
  164. 39
  165. 40
  166. 41
  167. 42
  168. 43
  169. </pre></td><td class="code"><pre>&lt;?php
  170. /**
  171. * post_tweet.php
  172. * Example of posting a tweet with OAuth
  173. * Latest copy of this code:
  174. *
  175. * @author Adam Green &lt;;
  176. * @license GNU Public License
  177. */
  178. $tweet_text = 'Hello Twitter';
  179. print &quot;Posting...\n&quot;;
  180. $result = post_tweet($tweet_text);
  181. print &quot;Response code: &quot; . $result . &quot;\n&quot;;
  182. function post_tweet($tweet_text) {
  183. // Use Matt Harris' OAuth library to make the connection
  184. // This lives at:
  185. require_once('tmhoauth/tmhOAuth.php');
  186. // Set the authorization values
  187. // In keeping with the OAuth tradition of maximum confusion,
  188. // the names of some of these values are different from the Twitter Dev interface
  189. // user_token is called Access Token on the Dev site
  190. // user_secret is called Access Token Secret on the Dev site
  191. // The values here have asterisks to hide the true contents
  192. // You need to use the actual values from Twitter
  193. $connection = new tmhOAuth(array(
  194. 'consumer_key' =&gt; '******',
  195. 'consumer_secret' =&gt; '******',
  196. 'user_token' =&gt; '******',
  197. 'user_secret' =&gt; '******',
  198. ));
  199. // Make the API call
  200. $connection-&gt;request('POST',
  201. $connection-&gt;url('1/statuses/update'),
  202. array('status' =&gt; $tweet_text));
  203. return $connection-&gt;response['code'];
  204. }
  205. ?&gt;</pre></td></tr></table>
  206. <p>You can see from the script that the API response code is available after the call in the connection object as <code>$connection->response['code']</code>. This is either 200 for a successful request, or one of the many possible <a href="">error codes</a>. </p>
  207. <p>You can also get the data returned by the API with <code>$connection->response['response']</code>. In the case of a tweet, the response returned is a complete tweet object, just as if you had looked up the tweet from a user&#8217;s timeline. </p>
  208. <h2>Running the test script</h2>
  209. <p>Post_tweet.php is meant to be used directly from a server, not a Web page. Here is what it looks like when run from a Linux server. </p>
  210. <p><img src="" border="1"></p>
  211. <p>The Twitter API returned a response code of 200, which means the tweet request was successful. Looking in the @140devdemo account shows the new tweet. Notice that the source listed for the tweet is the same as the name I gave the application. Clicking this source text will open the URL assigned to the application. </p>
  212. <p><img src="" border="1"></p>
  213. <p>Let&#8217;s test the app by running it again. </p>
  214. <p><img src="" border="1"></p>
  215. <p>This time a 403 code was returned. This is an error code that can have many meanings, but in general it means that the API request was rejected. In this case that is because Twitter doesn&#8217;t allow duplicate tweets. </p>
  216. <p>Now you can include the post_tweet.php script in your own code and pass a string to <code>post_tweet()</code> to have it tweeted. By extracting the proper segment of any API call and getting the right parameter name, as shown above, you can construct equally simple wrapper functions for any part of the Twitter API.</p>
  217. <h2>Applying this code to other API calls</h2>
  218. <p>Still a little confused how to map API docs into actual PHP code? This handy, dandy map should help:</p>
  219. <p><img src="" border="1"></p>
  220. <h2>Download the tutorial files</h2>
  221. <p>If you want to try out this sample code yourself, you can download this <a href="">zip file</a> with a copy of the Matt Harris OAuth library and the post_tweet.php script. </p>
  222. </div>
  223. </div>
  224. </div>
  225. <div id="sidebars">
  226. <div id="sidebar_1" class="sidebar">
  227. <ul class="sidebar_list">
  228. <li id="text-5" class="widget widget_text"><img src="/blog_images/AdamGreen.jpg" style="margin-bottom: 5px; float: left; margin-right: 12px;"><h3 style="font-size:15px;margin-top: 0px;">Hire Adam Green to Develop Custom Twitter Solutions</h3>
  229. <div class="textwidget">Contact Adam for a free initial consultation
  230. <br/> by phone at (781) 879-2960
  231. <br/> or email at <a style="color:#000;text-decoration:none;" href=""></a>
  232. <br/> <a href=""><u>Learn More</u></a></div>
  233. </li><li style="height: 30px;"><h3 style="float: left; margin-left: 48px;margin-bottom:0px;">Our Projects</h3><div id="change_proj"><div id="prev_proj"></div><div id="next_proj"></div></div></li>
  234. <li id="text-9" class="widget widget_text">
  235. <div id="our_projects" style="">
  236. <div class="project proj1">
  237. <b>2012twit</b><br>
  238. <span><a href="" target="_blank">Real-Time Tracking of the 2012 Election</a></span>
  239. <p style="text-align: center; margin-top: 8px;"><a href="" target="_blank"><img src="/blog_images/2012twit_290.png"></a></p>
  240. </div>
  241. <div class="project proj2">
  242. <b>DirectSnap</b><br>
  243. <span><a href="">College Football Recruiting</a></span>
  244. <p style="text-align: center; margin-top: 8px;"><a href="" target="_blank"><img src="/blog_images/directsnap.png"></a></p>
  245. </div>
  246. <div class="project proj3">
  247. <b>2012GOP</b><br>
  248. <span><a href="">Follow GOP candidates fighting for <br>the 2012 Presidential Election on Twitter!</a></span>
  249. <p style="text-align: center; margin-top: 8px;"><a href=""><img style="border: 0px none;" src="/blog_images/AppStore_290.png"></a></p>
  250. </div>
  251. <div class="project proj4">
  252. <b>This Or That</b><br>
  253. <span><a href="">A fun way to watch a real-time comparison between any two topics on Twitter.</a></span>
  254. <p style="text-align: center; margin-top: 8px;"><a href="" target="_blank"><img src="/blog_images/thsrtht_thumb.png"></a></p>
  255. </div>
  256. <div class="project proj5">
  257. <b>140townhall</b><br>
  258. <span><a href="" target="_blank">The First Presidential Debate on Twitter</a></span>
  259. <p style="text-align: center; margin-top: 8px;"><a href="" target="_blank"><img src="/blog_images/140townhall_290.png"></a></p>
  260. </div>
  261. <div class="project proj6">
  262. <b>Donate Tweets</b><br>
  263. <span><a href="">Donate One Tweet a Day to Buddy Roemer 2012</a></span>
  264. <p style="text-align: center; margin-top: 8px;"><a href="" target="_blank"><img src="/blog_images/donate_tweets_275.png"></a></p>
  265. </div>
  266. <div class="project proj7">
  267. <b>140elect</b><br>
  268. <span><a href="">Twitter Campaigns for the 2012 Election - <br/>Tools, Metrics, and Strategy</a></span>
  269. <p style="text-align: center; margin-top: 8px;"><a href="" target="_blank"><img src="/blog_images/140elect_290.png"></a></p>
  270. </div>
  271. </div>
  272. </li>
  273. <h3 style="">Testimonials</h3>
  274. <div style="margin-bottom:12px;" id="testimonials">
  275. <blockquote style="padding-left:12px;">I have worked with a ton of developers over the years, and the guys at 140dev are as good as it gets. They built exactly what I asked them to, got it done quickly, and communicated consistently throughout the process. Equally impressive was the fact that they took the time up front to explain many of limitations and opportunities with the Twitter API, which not only helped me refine my project, but saved me a considerable amount of time. I hope to work with them again and can not recommend them highly enough."</blockquote>
  276. <p style="text-align:right;margin-bottom:16px;"><b>- <a href="">Justin Feinstein</a>, <a target="_blank" href=""></a></b></p>
  277. <blockquote style="padding-left:12px;">Adam and the 140 Dev team are more than just developers. They take ownership over the project in an effort to produce the highest quality code and end-product for users. Their knowledge of the Twitter API, overall system architecture and web-based interface design is top notch. We would highly recommend the 140 Dev team and will be using them on future projects."</blockquote>
  278. <p style="text-align:right;"><b>- <span>Kevin Duffey</span>, <a target="_blank" href=""></a></b></p>
  279. </div> <li class="widget widget_recent_entries" id="recent-posts-3"> <h3>Recent Blog Posts</h3> <ul>
  280. <li><a href="" title="Initial impressions of Rackspace&#8217;s cloud servers">Initial impressions of Rackspace&#8217;s cloud servers</a></li>
  281. <li><a href="" title="Dealing with tweet bursts">Dealing with tweet bursts</a></li>
  282. <li><a href="" title="Twitter API Tutorial: Identifying the best Twitter accounts for following">Twitter API Tutorial: Identifying the best Twitter accounts for following</a></li>
  283. <li><a href="" title="Secrets of a donated tweet system">Secrets of a donated tweet system</a></li>
  284. <li><a href="" title="Screening a tweet stream for quality control">Screening a tweet stream for quality control</a></li>
  285. <li><a href="" title="Exceeding the search API rate limit">Exceeding the search API rate limit</a></li>
  286. <li><a href="" title="Dealing with 500 errors when retrieving user data">Dealing with 500 errors when retrieving user data</a></li>
  287. <li><a href="" title="New iPhone app based on the 2012twit database">New iPhone app based on the 2012twit database</a></li>
  288. <li><a href="" title="Collecting #OWS tweets with the 140dev framework">Collecting #OWS tweets with the 140dev framework</a></li>
  289. <li><a href="" title="Primer for Automated Twitter Engagement">Primer for Automated Twitter Engagement</a></li>
  290. </ul>
  291. </li><li class="widget widget_text" id="text-6"><h3>Recent Twitter API Programming Tutorials</h3> <div class="textwidget"><a href="" title="Identifying the best Twitter accounts for following">Identifying the best Twitter accounts for following</a><br /><br /><a href="" title="How to post tweets with Twitter OAuth and PHP">Hello Twitter OAuth with PHP</a><br /><br /><a href="" title="Identifying influential Twitter users">Identifying influential Twitter users</a><br /><br />
  292. <a href="" title="Twitter Search API vs. Streaming API">Aggregating tweets: Search API vs. Streaming API</a><br /><br />
  293. <a href="" title="Making aggregated tweets visible to Google for SEO">Making aggregated tweets visible to Google for SEO</a><br /><br />
  294. <a href="" title="Advantages of a Twitter API database cache">Advantages of a Twitter API database cache</a></div>
  295. </li><li class="widget widget_categories" id="categories-3"><h3>Blog Categories</h3> <ul>
  296. <li class="cat-item cat-item-20"><a href="" title="View all posts filed under 140dev Source Code">140dev Source Code</a>
  297. </li>
  298. <li class="cat-item cat-item-43"><a href="" title="View all posts filed under API error">API error</a>
  299. </li>
  300. <li class="cat-item cat-item-29"><a href="" title="View all posts filed under Automated following">Automated following</a>
  301. </li>
  302. <li class="cat-item cat-item-14"><a href="" title="View all posts filed under Automated Tweets">Automated Tweets</a>
  303. </li>
  304. <li class="cat-item cat-item-34"><a href="" title="View all posts filed under Church of Twitter">Church of Twitter</a>
  305. </li>
  306. <li class="cat-item cat-item-10"><a href="" title="View all posts filed under Consulting Tips">Consulting Tips</a>
  307. </li>
  308. <li class="cat-item cat-item-26"><a href="" title="View all posts filed under Custom Twitter Client">Custom Twitter Client</a>
  309. </li>
  310. <li class="cat-item cat-item-13"><a href="" title="View all posts filed under Data Mining Tweets">Data Mining Tweets</a>
  311. </li>
  312. <li class="cat-item cat-item-15"><a href="" title="View all posts filed under Database Cache">Database Cache</a>
  313. </li>
  314. <li class="cat-item cat-item-40"><a href="" title="View all posts filed under Education">Education</a>
  315. </li>
  316. <li class="cat-item cat-item-16"><a href="" title="View all posts filed under Integrating Twitter with Wordpress">Integrating Twitter with Wordpress</a>
  317. </li>
  318. <li class="cat-item cat-item-42"><a href="" title="View all posts filed under iPhone app">iPhone app</a>
  319. </li>
  320. <li class="cat-item cat-item-33"><a href="" title="View all posts filed under MSM on Twitter">MSM on Twitter</a>
  321. </li>
  322. <li class="cat-item cat-item-39"><a href="" title="View all posts filed under Phirehose">Phirehose</a>
  323. </li>
  324. <li class="cat-item cat-item-44"><a href="" title="View all posts filed under Quality Control">Quality Control</a>
  325. </li>
  326. <li class="cat-item cat-item-9"><a href="" title="View all posts filed under Rate Limits">Rate Limits</a>
  327. </li>
  328. <li class="cat-item cat-item-18"><a href="" title="View all posts filed under Sales Leads">Sales Leads</a>
  329. </li>
  330. <li class="cat-item cat-item-17"><a href="" title="View all posts filed under Search API">Search API</a>
  331. </li>
  332. <li class="cat-item cat-item-45"><a href="" title="View all posts filed under Server configuration">Server configuration</a>
  333. </li>
  334. <li class="cat-item cat-item-7"><a href="" title="View all posts filed under Streaming API">Streaming API</a>
  335. </li>
  336. <li class="cat-item cat-item-35"><a href="" title="View all posts filed under The future of Twitter">The future of Twitter</a>
  337. </li>
  338. <li class="cat-item cat-item-22"><a href="" title="View all posts filed under The next wave">The next wave</a>
  339. </li>
  340. <li class="cat-item cat-item-28"><a href="" title="View all posts filed under Truthytweets">Truthytweets</a>
  341. </li>
  342. <li class="cat-item cat-item-8"><a href="" title="View all posts filed under Tweet Aggregation">Tweet Aggregation</a>
  343. </li>
  344. <li class="cat-item cat-item-25"><a href="" title="View all posts filed under Tweet Display">Tweet Display</a>
  345. </li>
  346. <li class="cat-item cat-item-32"><a href="" title="View all posts filed under Twitter Advertising">Twitter Advertising</a>
  347. </li>
  348. <li class="cat-item cat-item-31"><a href="" title="View all posts filed under Twitter Analytics">Twitter Analytics</a>
  349. </li>
  350. <li class="cat-item cat-item-4"><a href="" title="View all posts filed under Twitter API Tutorials">Twitter API Tutorials</a>
  351. </li>
  352. <li class="cat-item cat-item-5"><a href="" title="View all posts filed under Twitter Developers">Twitter Developers</a>
  353. </li>
  354. <li class="cat-item cat-item-23"><a href="" title="View all posts filed under Twitter Ecosystem">Twitter Ecosystem</a>
  355. </li>
  356. <li class="cat-item cat-item-41"><a href="" title="View all posts filed under Twitter Engagement Campaign">Twitter Engagement Campaign</a>
  357. </li>
  358. <li class="cat-item cat-item-11"><a href="" title="View all posts filed under Twitter Marketing">Twitter Marketing</a>
  359. </li>
  360. <li class="cat-item cat-item-27"><a href="" title="View all posts filed under Twitter OAuth">Twitter OAuth</a>
  361. </li>
  362. <li class="cat-item cat-item-24"><a href="" title="View all posts filed under Twitter Politics">Twitter Politics</a>
  363. </li>
  364. <li class="cat-item cat-item-36"><a href="" title="View all posts filed under Twitter SEO">Twitter SEO</a>
  365. </li>
  366. <li class="cat-item cat-item-37"><a href="" title="View all posts filed under Twitter Server Errors">Twitter Server Errors</a>
  367. </li>
  368. <li class="cat-item cat-item-1"><a href="" title="View all posts filed under Uncategorized">Uncategorized</a>
  369. </li>
  370. <li class="cat-item cat-item-21"><a href="" title="View all posts filed under User Ranking">User Ranking</a>
  371. </li>
  372. </ul>
  373. </li> </ul>
  374. </div>
  375. </div>
  376. </div>
  377. <div id="footer">
  378. <p>&copy; 2010 by 140 Dev, LLC</p> </div>
  379. </div>
  380. </div>
  381. <!--[if lte IE 8]>
  382. <div id="ie_clear"></div>
  383. <![endif]-->
  384. <script type="text/javascript">
  385. var _gaq = _gaq || [];
  386. _gaq.push(['_setAccount', 'UA-19021021-1']);
  387. _gaq.push(['_trackPageview']);
  388. (function() {
  389. var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
  390. ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '';
  391. var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
  392. })();
  393. </script>
  394. </body>
  395. </html>