<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,3 +1,7 @@
+0.6.0 - April 11, 2009
+* 1 feature addition
+  * Added http authentication back in. You can now use oauth or http auth as your client.
+  
 0.5.3 - April 10, 2009
 * 1 minor fix
   * Twitter API assumed follow true whether true or false. Now only sending follow along to request if follow is true for calls to friendship_create.</diff>
      <filename>History</filename>
    </modified>
    <modified>
      <diff>@@ -1,9 +1,13 @@
 = twitter
 
-The ruby twitter gem. The gem heard round the world and famous on the streets. Haha.
+The ruby twitter gem. The gem heard round the world and famous on the streets. Haha. This gem works with both oauth and http auth, if you care.
 
 For now this is just an API wrapper. The command line interface is temporarily dead until I have time to make it work with oauth. At that point, I'll make it a new gem twitter-cli or something and it will depend on this gem to work. That will keep the separation of the api wrapper and cli and fix a lot of dependency issues.
 
+= examples
+  
+  See the examples directory.
+
 == Copyright
 
 Copyright (c) 2009 John Nunemaker. See LICENSE for details.</diff>
      <filename>README.rdoc</filename>
    </modified>
    <modified>
      <diff>@@ -23,13 +23,15 @@
 	&lt;div id=&quot;content&quot;&gt;
 	  &lt;h2&gt;Note&lt;/h2&gt;
 	  
-	  &lt;p&gt;The twitter gem now only supports OAuth as an authentication method. OAuth is scary at first, but not once you try it out a little bit. Feel free to read my &lt;a href=&quot;http://railstips.org/2009/3/29/oauth-explained-and-what-it-is-good-for&quot;&gt;article on OAuth&lt;/a&gt; to get past the scary part.&lt;/p&gt;
+	  &lt;p&gt;The Twitter gem supports OAuth and HTTP Auth (until Twitter deprecates it). OAuth is scary at first, but not once you try it out a little bit. Feel free to read my &lt;a href=&quot;http://railstips.org/2009/3/29/oauth-explained-and-what-it-is-good-for&quot;&gt;article on OAuth&lt;/a&gt; to get past the scary part. Also, I have created an &lt;a href=&quot;http://github.com/jnunemaker/twitter-app/&quot;&gt;example app&lt;/a&gt; that uses OAuth and the Twitter gem for you to peruse.&lt;/p&gt;
 	   
 		&lt;h2&gt;Install&lt;/h2&gt; 
 		&lt;pre&gt;&lt;code&gt;$ sudo gem install twitter&lt;/code&gt;&lt;/pre&gt;
 		
 		&lt;h2&gt;Examples&lt;/h2&gt;
 		
+		&lt;p&gt;First some OAuth action:&lt;/p&gt;
+		
 &lt;pre&gt;&lt;code&gt;# NOT SHOWN: granting access to twitter on website
 # and using request token to generate access token
 oauth = Twitter::OAuth.new('consumer token', 'consumer secret')
@@ -42,6 +44,14 @@ client.replies.each           { |tweet| puts tweet.inspect }
 
 client.update('Heeeyyyyoooo from Twitter Gem!')&lt;/code&gt;&lt;/pre&gt;
 		
+		&lt;p&gt;Now some HTTP Auth action:&lt;/p&gt;
+		
+&lt;pre&gt;&lt;code&gt;httpauth = Twitter::HTTPAuth.new('username', 'password')
+base = Twitter::Base.new(httpauth)
+base.update('Heeeeyyyyooo from the Twitter Gem')
+base.friends_timeline.each { |tweet| puts tweet.text }
+&lt;/code&gt;&lt;/pre&gt;
+		
 		&lt;h2&gt;Search API Examples&lt;/h2&gt;
 		
 &lt;pre&gt;&lt;code&gt;#searches all tweets for httparty</diff>
      <filename>website/index.html</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>d713ecfbe80edde688009fa6bfbf32a2de687a39</id>
    </parent>
  </parents>
  <author>
    <name>John Nunemaker</name>
    <email>nunemaker@gmail.com</email>
  </author>
  <url>http://github.com/jnunemaker/twitter/commit/2f032ed4e521ecb9b676d2f6a3f79f6632d384b8</url>
  <id>2f032ed4e521ecb9b676d2f6a3f79f6632d384b8</id>
  <committed-date>2009-04-10T22:55:59-07:00</committed-date>
  <authored-date>2009-04-10T22:52:23-07:00</authored-date>
  <message>Updated history, readme and website to reflect that http auth is supported.</message>
  <tree>9e4eab67df189a25575d910d3302d3c676b24ee4</tree>
  <committer>
    <name>John Nunemaker</name>
    <email>nunemaker@gmail.com</email>
  </committer>
</commit>
