<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Twitter to Implement OAuth as Future Authentication Method</title>
	<atom:link href="http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/feed/" rel="self" type="application/rss+xml" />
	<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/</link>
	<description>Microblogging News and Reviews for Platforms, Tools and Services</description>
	<lastBuildDate>Sat, 20 Mar 2010 14:44:15 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Bockenstedt</title>
		<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/#comment-630</link>
		<dc:creator>Mark Bockenstedt</dc:creator>
		<pubDate>Sat, 10 Jan 2009 19:18:15 +0000</pubDate>
		<guid isPermaLink="false">http://microblink.com/?p=2106#comment-630</guid>
		<description>&lt;b&gt;@Chris&lt;/b&gt;

Sounds great, I&#039;ll be sure to check it out. Thanks for sharing.</description>
		<content:encoded><![CDATA[<p><b>@Chris</b></p>
<p>Sounds great, I&#8217;ll be sure to check it out. Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/#comment-629</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Sat, 10 Jan 2009 19:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://microblink.com/?p=2106#comment-629</guid>
		<description>You might be interested in the podcast that Larry Halff (Ma.gnolia) and I did with Alex Payne on Twitter, security, phishing and OAuth the other day:

http://tr.im/cg_10</description>
		<content:encoded><![CDATA[<p>You might be interested in the podcast that Larry Halff (Ma.gnolia) and I did with Alex Payne on Twitter, security, phishing and OAuth the other day:</p>
<p><a href="http://tr.im/cg_10" rel="nofollow">http://tr.im/cg_10</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StevieB&#8217;s Shared Items - January 6, 2009 at Lost in Cyberspace</title>
		<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/#comment-592</link>
		<dc:creator>StevieB&#8217;s Shared Items - January 6, 2009 at Lost in Cyberspace</dc:creator>
		<pubDate>Tue, 06 Jan 2009 11:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://microblink.com/?p=2106#comment-592</guid>
		<description>[...] Twitter to Implement OAuth as Future Authentication MethodJanuary 5, 2009 [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter to Implement OAuth as Future Authentication MethodJanuary 5, 2009 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Brudtkuhl</title>
		<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/#comment-590</link>
		<dc:creator>Andy Brudtkuhl</dc:creator>
		<pubDate>Tue, 06 Jan 2009 05:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://microblink.com/?p=2106#comment-590</guid>
		<description>That clears it all up! That smells like a full on blog post :)</description>
		<content:encoded><![CDATA[<p>That clears it all up! That smells like a full on blog post <img src='http://microblink.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Bockenstedt</title>
		<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/#comment-589</link>
		<dc:creator>Mark Bockenstedt</dc:creator>
		<pubDate>Tue, 06 Jan 2009 03:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://microblink.com/?p=2106#comment-589</guid>
		<description>Andy
I agree that OpenID is more widely known than OAuth is since big names like AOL, Flickr, MySpace, and Yahoo have adopted it. OAuth benefits over standard authentication (username/password combo) in the fact that it&#039;s a standardized, secure way to authenticate against an API. I think Mashable put it best when they said:

&quot;OpenID solves the problem of having far too many usernames and passwords to remember. OAuth solves the problem of how to share information between sites without giving your password from one site to another.&quot;

The importance of OAuth is that it&#039;s standardized. There are no standards regarding safely storing or transmitting passwords - you could encrypt it, hash it, etc but there&#039;s nothing telling you what you must do. It&#039;s also really good at safely sharing information between sites and services, which is why it&#039;s an excellent fit for this scenario. There&#039;s a good example describing the process for both methods &lt;a href=&quot;http://cakebaker.42dh.com/2008/04/01/openid-versus-oauth-from-the-users-perspective/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. There&#039;s a complicated workflow for OAuth on how access is requested and granted &lt;a href=&quot;http://oauth.net/core/1.0/#anchor9&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Andy<br />
I agree that OpenID is more widely known than OAuth is since big names like AOL, Flickr, MySpace, and Yahoo have adopted it. OAuth benefits over standard authentication (username/password combo) in the fact that it&#8217;s a standardized, secure way to authenticate against an API. I think Mashable put it best when they said:</p>
<p>&#8220;OpenID solves the problem of having far too many usernames and passwords to remember. OAuth solves the problem of how to share information between sites without giving your password from one site to another.&#8221;</p>
<p>The importance of OAuth is that it&#8217;s standardized. There are no standards regarding safely storing or transmitting passwords &#8211; you could encrypt it, hash it, etc but there&#8217;s nothing telling you what you must do. It&#8217;s also really good at safely sharing information between sites and services, which is why it&#8217;s an excellent fit for this scenario. There&#8217;s a good example describing the process for both methods <a href="http://cakebaker.42dh.com/2008/04/01/openid-versus-oauth-from-the-users-perspective/" rel="nofollow">here</a>. There&#8217;s a complicated workflow for OAuth on how access is requested and granted <a href="http://oauth.net/core/1.0/#anchor9" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Brudtkuhl</title>
		<link>http://microblink.com/2009/01/05/twitter-to-implement-oauth-as-future-authentication-method/#comment-587</link>
		<dc:creator>Andy Brudtkuhl</dc:creator>
		<pubDate>Mon, 05 Jan 2009 21:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://microblink.com/?p=2106#comment-587</guid>
		<description>How is oAuth more secure than the current authorization system? Also - what&#039;s the benefit of oAuth over OpenID? Seems OpenId has been more widely adopted...</description>
		<content:encoded><![CDATA[<p>How is oAuth more secure than the current authorization system? Also &#8211; what&#8217;s the benefit of oAuth over OpenID? Seems OpenId has been more widely adopted&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
