<?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"
	>
<channel>
	<title>Comments on: OpenID &#038; OAuth Latency - Painful User Experience</title>
	<atom:link href="http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/feed/" rel="self" type="application/rss+xml" />
	<link>http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/</link>
	<description>Your One Stop Shop for Chinese Pop</description>
	<pubDate>Fri, 10 Sep 2010 16:39:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: http://openid.aol.com/MicroBerto</title>
		<link>http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/#comment-3697</link>
		<dc:creator>http://openid.aol.com/MicroBerto</dc:creator>
		<pubDate>Sun, 14 Oct 2007 22:28:02 +0000</pubDate>
		<guid isPermaLink="false">http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/#comment-3697</guid>
		<description>You are due for a new post!!!  Get cracken!</description>
		<content:encoded><![CDATA[<p>You are due for a new post!!!  Get cracken!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: =eran</title>
		<link>http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/#comment-3320</link>
		<dc:creator>=eran</dc:creator>
		<pubDate>Mon, 24 Sep 2007 02:40:50 +0000</pubDate>
		<guid isPermaLink="false">http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/#comment-3320</guid>
		<description>You are correct about the first 7 steps but once you get back to the Consumer everything else is done by the Consumer directly so no more redirects. This is still a bit of a hassle the first time you use services from that OpenID/Service Provider combo but unless you are one of those people wearing aluminum hats, your browser cookies are enabled and this gets much better on repeat usage.

There are no magic solutions. If you give your username and password to the Consumer, yes, they do all this for you but can also do anything they want and the only way to stop them is by changing your password (assuming they didn’t beat you to it and hijacked your account). If you don’t, you need a way to give them something you approved.

There are ways to make this better for the user experience but usually at a price of security.</description>
		<content:encoded><![CDATA[<p>You are correct about the first 7 steps but once you get back to the Consumer everything else is done by the Consumer directly so no more redirects. This is still a bit of a hassle the first time you use services from that OpenID/Service Provider combo but unless you are one of those people wearing aluminum hats, your browser cookies are enabled and this gets much better on repeat usage.</p>
<p>There are no magic solutions. If you give your username and password to the Consumer, yes, they do all this for you but can also do anything they want and the only way to stop them is by changing your password (assuming they didn’t beat you to it and hijacked your account). If you don’t, you need a way to give them something you approved.</p>
<p>There are ways to make this better for the user experience but usually at a price of security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/#comment-3318</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Sun, 23 Sep 2007 20:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://sinopop.net/2007/09/23/openid-oauth-latency-painful-user-experience/#comment-3318</guid>
		<description>This is an excellent point -- and one that admittedly gets obfuscated in the process of developing protocols. 

That said, I think that this problem goes away over time as connectivity improves and I also think that the initial time-cost of authenticating in series of steps becomes both regular, easier as interfaces improve, and better yet as we move away from username/password combos being replaced by biometrics or other types of verification.

Additionally, the idea is that as browsers get better at things like OpenID and so on, this whole dance will become a lot easier, just as on the desktop you can limit which apps are allowed to do different things. 

All these technologies have a long way to go and it's important to point out issues like this. At the same time, I don't think that we should accept that spreading username and passwords all over the place is a good solution either, so until we have something better, this is the best we've got for the moment.</description>
		<content:encoded><![CDATA[<p>This is an excellent point &#8212; and one that admittedly gets obfuscated in the process of developing protocols. </p>
<p>That said, I think that this problem goes away over time as connectivity improves and I also think that the initial time-cost of authenticating in series of steps becomes both regular, easier as interfaces improve, and better yet as we move away from username/password combos being replaced by biometrics or other types of verification.</p>
<p>Additionally, the idea is that as browsers get better at things like OpenID and so on, this whole dance will become a lot easier, just as on the desktop you can limit which apps are allowed to do different things. </p>
<p>All these technologies have a long way to go and it&#8217;s important to point out issues like this. At the same time, I don&#8217;t think that we should accept that spreading username and passwords all over the place is a good solution either, so until we have something better, this is the best we&#8217;ve got for the moment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
