<?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: Is OpenID the future?</title>
	<atom:link href="http://blog.increosolutions.com/2009/03/is-openid-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.increosolutions.com/2009/03/is-openid-the-future/</link>
	<description>Increo Solutions Corporate Blog</description>
	<pubDate>Sun, 05 Feb 2012 08:50:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AndrewBoldman</title>
		<link>http://blog.increosolutions.com/2009/03/is-openid-the-future/comment-page-1/#comment-6178</link>
		<dc:creator>AndrewBoldman</dc:creator>
		<pubDate>Thu, 04 Jun 2009 15:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.increosolutions.com/2009/03/is-openid-the-future/#comment-6178</guid>
		<description>Hi, cool post. I have been wondering about this topic,so thanks for writing.</description>
		<content:encoded><![CDATA[<p>Hi, cool post. I have been wondering about this topic,so thanks for writing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://blog.increosolutions.com/2009/03/is-openid-the-future/comment-page-1/#comment-6060</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Wed, 25 Mar 2009 10:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.increosolutions.com/2009/03/is-openid-the-future/#comment-6060</guid>
		<description>Two problems I have with OpenID (or implementations of it I've seen) - along with your "Two steps forward, one step back" point (which I also think is very valid):

1) Sites often use OpenID for authentication, but then make you /also/ create a local profile before you can do anything.  As a user, it feels like an added extra step of complexity for no reason.

2) I feel a little uneasy about logging in everywhere with one 'account':
     • It gives the provider (AOL or Google, say) yet another way to track my web usage habits.
     • It means that there's a single point of failure - if someone cracks my password, they can now log in anywhere (I know, this is the same problem as if I use the same password everywhere, but I think that, psychologically, it feels more 'real' when the actual sign-in process is also the same).
     • Single point of failure in reverse: what happens in the future if I'm using, say, my AIM account as OpenID everywhere, but I decide I want to delete my AIM account?
     • When my OpenID ID is used as a user name (which is somewhat necessary to allow, given that the alternative is to go the way of my point 1, which is also annoying), it means that anyone who knows my account in one place can now find my account in any other place.  

My logical brain tells me that point 2's subpoints are mainly just paranoia, but that doesn't take away the bad feelings.

I think though that if my point 1 were addressed - i.e. if OpenID worked to the extent that I could just go to a new site, log in, do nothing further, and everything worked, the sheer convenience would probably cancel out my concerns in point 2.  As it stands, using OpenID (as a user) on an arbitrary site is often more complex than not using it.</description>
		<content:encoded><![CDATA[<p>Two problems I have with OpenID (or implementations of it I&#8217;ve seen) - along with your &#8220;Two steps forward, one step back&#8221; point (which I also think is very valid):</p>
<p>1) Sites often use OpenID for authentication, but then make you /also/ create a local profile before you can do anything.  As a user, it feels like an added extra step of complexity for no reason.</p>
<p>2) I feel a little uneasy about logging in everywhere with one &#8216;account&#8217;:<br />
     • It gives the provider (AOL or Google, say) yet another way to track my web usage habits.<br />
     • It means that there&#8217;s a single point of failure - if someone cracks my password, they can now log in anywhere (I know, this is the same problem as if I use the same password everywhere, but I think that, psychologically, it feels more &#8216;real&#8217; when the actual sign-in process is also the same).<br />
     • Single point of failure in reverse: what happens in the future if I&#8217;m using, say, my AIM account as OpenID everywhere, but I decide I want to delete my AIM account?<br />
     • When my OpenID ID is used as a user name (which is somewhat necessary to allow, given that the alternative is to go the way of my point 1, which is also annoying), it means that anyone who knows my account in one place can now find my account in any other place.  </p>
<p>My logical brain tells me that point 2&#8217;s subpoints are mainly just paranoia, but that doesn&#8217;t take away the bad feelings.</p>
<p>I think though that if my point 1 were addressed - i.e. if OpenID worked to the extent that I could just go to a new site, log in, do nothing further, and everything worked, the sheer convenience would probably cancel out my concerns in point 2.  As it stands, using OpenID (as a user) on an arbitrary site is often more complex than not using it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

