<?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: The Single Sign-On War Will Ruin OpenID</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sat, 07 Nov 2009 23:35:20 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joseph Engo</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818568</link>
		<dc:creator>Joseph Engo</dc:creator>
		<pubDate>Thu, 30 Oct 2008 21:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818568</guid>
		<description>I am a big supporter of OpenID, I use it in all of my projects.  However, what Google is doing is NOT supporting OpenID.  They are taking an open specification and destroying it with their own vision.  Sorry, it doesn&#039;t work that way.  Either you want to support OpenID or you don&#039;t.

If Google or MSN want to create their own system, go for it.  But claiming its OpenID is bullshit.

Yahoo is pulling the same crap. Requesting developers put a &quot;sign in with Yahoo&quot; logo is retarded and defeats the point.</description>
		<content:encoded><![CDATA[<p>I am a big supporter of OpenID, I use it in all of my projects.  However, what Google is doing is NOT supporting OpenID.  They are taking an open specification and destroying it with their own vision.  Sorry, it doesn&#8217;t work that way.  Either you want to support OpenID or you don&#8217;t.</p>
<p>If Google or MSN want to create their own system, go for it.  But claiming its OpenID is bullshit.</p>
<p>Yahoo is pulling the same crap. Requesting developers put a &#8220;sign in with Yahoo&#8221; logo is retarded and defeats the point.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AlexW</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818538</link>
		<dc:creator>AlexW</dc:creator>
		<pubDate>Thu, 30 Oct 2008 20:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818538</guid>
		<description>&lt;blockquote&gt; It is up the author to filter their own work, they shouldn’t be filtering their feedback.&lt;/blockquote&gt;

Because it&#039;s everyone&#039;s god given right to spam and troll! You&#039;ll get my submit button when you you pry it from my cold dead fingers.</description>
		<content:encoded><![CDATA[<blockquote><p> It is up the author to filter their own work, they shouldn’t be filtering their feedback.</p></blockquote>
<p>Because it&#8217;s everyone&#8217;s god given right to spam and troll! You&#8217;ll get my submit button when you you pry it from my cold dead fingers.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Will Norris</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818496</link>
		<dc:creator>Will Norris</dc:creator>
		<pubDate>Thu, 30 Oct 2008 19:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818496</guid>
		<description>I would highly recommend everyone watch the latest episode of TheSocialWeb.tv, in which Eric Sachs of Google talks about their OpenID.  Google is not opposed to being a consumer of externally authenticated users (in fact, they already DO with Google Apps)... there are just much more difficult problems when the service provider doesn&#039;t have a way to directly authenticate the user.

http://www.thesocialweb.tv/blog/2008/10/episode-16-open.html</description>
		<content:encoded><![CDATA[<p>I would highly recommend everyone watch the latest episode of TheSocialWeb.tv, in which Eric Sachs of Google talks about their OpenID.  Google is not opposed to being a consumer of externally authenticated users (in fact, they already DO with Google Apps)&#8230; there are just much more difficult problems when the service provider doesn&#8217;t have a way to directly authenticate the user.</p>
<p><a href="http://www.thesocialweb.tv/blog/2008/10/episode-16-open.html" rel="nofollow">http://www.thesocialweb.tv/blog/2008/10/episode-16-open.html</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stop Tracking me</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818445</link>
		<dc:creator>Stop Tracking me</dc:creator>
		<pubDate>Thu, 30 Oct 2008 17:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818445</guid>
		<description>Who cares, you shouldn&#039;t require any authentication for a user to post. I shouldn&#039;t have to provide you with any details in order for me to communicate and point out why your post is:
* dumb
* wrong
* not worth posting
* a silly idea

etc. It is up the author to filter their own work, they shouldn&#039;t be filtering their feedback.</description>
		<content:encoded><![CDATA[<p>Who cares, you shouldn&#8217;t require any authentication for a user to post. I shouldn&#8217;t have to provide you with any details in order for me to communicate and point out why your post is:<br />
* dumb<br />
* wrong<br />
* not worth posting<br />
* a silly idea</p>
<p>etc. It is up the author to filter their own work, they shouldn&#8217;t be filtering their feedback.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Deron Meranda</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818432</link>
		<dc:creator>Deron Meranda</dc:creator>
		<pubDate>Thu, 30 Oct 2008 16:52:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818432</guid>
		<description>Just to present the other side.  There are some reasonable arguments for why the big players should be cautious in being RPs too.

It may defeat some of their anti-spammer mechanisms surrounding the prevention of bulk or automated account creation.  This can probably be solved with OpenID, but it does require some non-trivial attention.

Most people only have one account at one of the big players; sure technical people may have multiple accounts at Yahoo!, Google, etc..., but I think that is pretty rare.  So for the people who only use one email account, they just won&#039;t see the problem of still having to remember multiple passwords.

If one of their email accounts gets hacked; they may have some legal liability, or at least bad PR to content with.  It&#039;s bad enough when Yahoo! gets a lot of bad press when Palin&#039;s account was cracked; imagine what would happen if a third-party OP was also in the mix.  Yahoo! would still get all the bad attention, but the breach wouldn&#039;t even be their fault or under their control.

Also, the big guys are, hopefully, much more security savy than smaller sites.  They have the capacity to correctly and securely manage logins, encrypt passwords, deal with password recovery, protecting against bot accounts, and so on.  Also they can tend to be a little more protective over user&#039;s privacy (or at least have more money and layers); sure it&#039;s not perfect, but Google is going to resist pretty hard when some company says it needs the name of the user for an account; without some sort of legal warrant.  I&#039;m not sure all the smaller OPs out there are as &quot;secure&quot; or trustworthy, so the big players should be concerned that this could jeopardize it&#039;s user&#039;s privacy when it outsources authentication to another party.


This is not to say that we shouldn&#039;t pressure them to become RPs as well, but we should appreciate that there are some special circumstances for them that need some careful thought.  I think some of that is just a matter of time, allowing OpenID to mature more.

Also, unless you are one of the few big players (Google, Yahoo!), then you should be an RP.  The arguments for being an OP only is not nearly as defensible.

Deron Meranda</description>
		<content:encoded><![CDATA[<p>Just to present the other side.  There are some reasonable arguments for why the big players should be cautious in being RPs too.</p>
<p>It may defeat some of their anti-spammer mechanisms surrounding the prevention of bulk or automated account creation.  This can probably be solved with OpenID, but it does require some non-trivial attention.</p>
<p>Most people only have one account at one of the big players; sure technical people may have multiple accounts at Yahoo!, Google, etc&#8230;, but I think that is pretty rare.  So for the people who only use one email account, they just won&#8217;t see the problem of still having to remember multiple passwords.</p>
<p>If one of their email accounts gets hacked; they may have some legal liability, or at least bad PR to content with.  It&#8217;s bad enough when Yahoo! gets a lot of bad press when Palin&#8217;s account was cracked; imagine what would happen if a third-party OP was also in the mix.  Yahoo! would still get all the bad attention, but the breach wouldn&#8217;t even be their fault or under their control.</p>
<p>Also, the big guys are, hopefully, much more security savy than smaller sites.  They have the capacity to correctly and securely manage logins, encrypt passwords, deal with password recovery, protecting against bot accounts, and so on.  Also they can tend to be a little more protective over user&#8217;s privacy (or at least have more money and layers); sure it&#8217;s not perfect, but Google is going to resist pretty hard when some company says it needs the name of the user for an account; without some sort of legal warrant.  I&#8217;m not sure all the smaller OPs out there are as &#8220;secure&#8221; or trustworthy, so the big players should be concerned that this could jeopardize it&#8217;s user&#8217;s privacy when it outsources authentication to another party.</p>
<p>This is not to say that we shouldn&#8217;t pressure them to become RPs as well, but we should appreciate that there are some special circumstances for them that need some careful thought.  I think some of that is just a matter of time, allowing OpenID to mature more.</p>
<p>Also, unless you are one of the few big players (Google, Yahoo!), then you should be an RP.  The arguments for being an OP only is not nearly as defensible.</p>
<p>Deron Meranda</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818404</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 30 Oct 2008 15:12:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818404</guid>
		<description>Otherwise if they are going to have their own then all pre-existing yahoo, or msn accounts should use the MSN or Yahoo provider but new logins should be accepted from anywhere.</description>
		<content:encoded><![CDATA[<p>Otherwise if they are going to have their own then all pre-existing yahoo, or msn accounts should use the MSN or Yahoo provider but new logins should be accepted from anywhere.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: futbalo.com</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818339</link>
		<dc:creator>futbalo.com</dc:creator>
		<pubDate>Thu, 30 Oct 2008 10:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818339</guid>
		<description>They don&#039;t want to implement fully the concept of OpenID cause they are big fishes who still want to be the center in a decentralized net. However it doesn&#039;t mean the concept of OpenID is screwed, let&#039;s see how things evolve when that technology becomes mainstream.</description>
		<content:encoded><![CDATA[<p>They don&#8217;t want to implement fully the concept of OpenID cause they are big fishes who still want to be the center in a decentralized net. However it doesn&#8217;t mean the concept of OpenID is screwed, let&#8217;s see how things evolve when that technology becomes mainstream.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stormrider</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818338</link>
		<dc:creator>Stormrider</dc:creator>
		<pubDate>Thu, 30 Oct 2008 10:21:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818338</guid>
		<description>The trouble is, if one of them says they will accept sign ins from other places, they won&#039;t get any signups themselves because people could just use other providers instead of theirs.

They all need to agree to accept others at once. It isn&#039;t going to happen on its own.</description>
		<content:encoded><![CDATA[<p>The trouble is, if one of them says they will accept sign ins from other places, they won&#8217;t get any signups themselves because people could just use other providers instead of theirs.</p>
<p>They all need to agree to accept others at once. It isn&#8217;t going to happen on its own.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Twylite</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818321</link>
		<dc:creator>Twylite</dc:creator>
		<pubDate>Thu, 30 Oct 2008 08:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818321</guid>
		<description>This is great news!  OpenID will be fragmented and eventually die, leaving the market open for a &lt;b&gt;secure&lt;/b&gt; standard that also has &lt;b&gt;privacy guarding&lt;/b&gt; features.</description>
		<content:encoded><![CDATA[<p>This is great news!  OpenID will be fragmented and eventually die, leaving the market open for a <b>secure</b> standard that also has <b>privacy guarding</b> features.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Wardrop</title>
		<link>http://www.sitepoint.com/blogs/2008/10/30/the-single-sign-on-war-will-ruin-openid/comment-page-1/#comment-818269</link>
		<dc:creator>Wardrop</dc:creator>
		<pubDate>Thu, 30 Oct 2008 04:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3139#comment-818269</guid>
		<description>It&#039;s just like the browser wars, everyone thinks that their own standards (for whatever reason) are better than the official W3C recommendations. Why is everything in life so frustrating, browsers, OpenID... what next, is someone going to bring out a cereal where you have to pour the cereal over the milk?</description>
		<content:encoded><![CDATA[<p>It&#8217;s just like the browser wars, everyone thinks that their own standards (for whatever reason) are better than the official W3C recommendations. Why is everything in life so frustrating, browsers, OpenID&#8230; what next, is someone going to bring out a cereal where you have to pour the cereal over the milk?</p>]]></content:encoded>
	</item>
</channel>
</rss>
