<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 23 May 2013 10:32:40 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Twitter OAuth]]></title>
      <guid>http://www.phpdeveloper.org/news/15145</guid>
      <link>http://www.phpdeveloper.org/news/15145</link>
      <description><![CDATA[<p>
<i>Chris Shiflett</i> has <a href="http://shiflett.org/blog/2010/sep/twitter-oauth">a new post</a> to his blog today about the new authentication model Twitter uses, OAuth, and how you can connect your PHP applications to their services.
</p>
<blockquote>
I've been working on a project with <a href="http://analog.coop/">my Analog friends</a> that might use the <a href="http://apiwiki.twitter.com/">Twitter API</a> to streamline stuff like signup for those who already use <a href="http://twitter.com/">Twitter</a>. Because this now requires <a href="http://blog.twitter.com/2010/08/twitter-applications-and-oauth.html">OAuth</a>, I needed to implement OAuth quickly, so that we had something to test and consider.
</blockquote>
<p>
He chose <a href="http://github.com/abraham/twitteroauth/downloads">this Twitter library</a> to connect his application and mentions the consumer key and consumer secret you'll nee to get from the <a href="http://dev.twitter.com/apps">Twitter development site</a>. The library makes it as simple as passing these bits of information in and having the Twitter side handle it from there (a redirect to approval page). The callback URL is requested and you then have access to that user's information including name, location, URL and description.
</p>]]></description>
      <pubDate>Fri, 17 Sep 2010 08:48:59 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[SitePoint.com: OAuth for PHP Twitter Apps, Part I]]></title>
      <guid>http://www.phpdeveloper.org/news/15073</guid>
      <link>http://www.phpdeveloper.org/news/15073</link>
      <description><![CDATA[<p>
On the SitePoint blogs today there's <a href="http://articles.sitepoint.com/article/oauth-for-php-twitter-apps-part-1">a new tutorial posted</a>, the first part of a series, from <i>Raj Deut</i> about making the move away from the basic authorization for connecting to the <a href="http://twitter.com">Twitter API</a> and towards their new OAuth method for <a href="http://dev.twitter.com/apps">Twitter Apps</a>.
</p>
<blockquote>
As of August 31, Twitter's HTTP Basic Authenticated API service has been disabled entirely. Now, any interface with the API will be required to use a token-based authentication method known an OAuth. [...] At first glance, the task of implementing OAuth can appear daunting, and OAuth's token exchange system can be confusing if you're unfamiliar with it. Fortunately, there are some rather clever individuals who've done the groundwork for us.
</blockquote>
<p>
They show you how to <a href="http://dev.twitter.com/apps">register your application</a> with Twitter and use the <a href="http://github.com/abraham/twitteroauth/downloads">TwitterOAuth library</a> to make a sample connection to their servers. They also show how to generate the tokens for the URL and the ones for accessing the site as a user. With tokens in hand, the script can then connect to the system and make a sample tweet (complete code included).
</p>]]></description>
      <pubDate>Fri, 03 Sep 2010 10:53:45 -0500</pubDate>
    </item>
  </channel>
</rss>
