<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: WordPress &amp; OpenID: Not really!</title>
	<atom:link href="http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/feed/" rel="self" type="application/rss+xml" />
	<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/</link>
	<description>A blog on Web Usability and Web 2.0</description>
	<lastBuildDate>Sun, 20 Sep 2009 07:44:24 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: WordPress / OpenID &#171; Jerome Baum - Weblog</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-551</link>
		<dc:creator>WordPress / OpenID &#171; Jerome Baum - Weblog</dc:creator>
		<pubDate>Sun, 30 Dec 2007 16:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-551</guid>
		<description>[...] a look at this blog post. I couldn&#8217;t agree more. WordPress cannot state that they &#8220;support&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] a look at this blog post. I couldn&#8217;t agree more. WordPress cannot state that they &#8220;support&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress.com+OpenID -- some ideas &#171; abakus</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-132</link>
		<dc:creator>Wordpress.com+OpenID -- some ideas &#171; abakus</dc:creator>
		<pubDate>Mon, 16 Apr 2007 13:50:02 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-132</guid>
		<description>[...] then, there has been some discussion about whether or not should wp.com become OpenID consumer, and what benefits wold that [...]</description>
		<content:encoded><![CDATA[<p>[...] then, there has been some discussion about whether or not should wp.com become OpenID consumer, and what benefits wold that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Brandt</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-128</link>
		<dc:creator>Bob Brandt</dc:creator>
		<pubDate>Sat, 14 Apr 2007 15:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-128</guid>
		<description>It&#039;s nice that Wordpress offers OpenIDs to its users, but not everyone will want to be forced to use Wordpress as their exclusive OpenID provider.  The Microsoft passport example is a good one, and people should remember that and heed it well.

Beyond the most important factor, Trust, there are many reasons for this:  logisitcs (someone already has an OpenID elsewhere), strenght of authentication (someone has an OpenID provider that offers very strong Identity protection for them at login - such as a biometric,e tc.), long term viability of wordpress as a site or IdP (people need to know that they will have longterm and full control of their own Identities), and inverse trust -- someone I choose to trust also trusting and vetting me before establishing my identity with them (you can&#039;t get a passport for example, without 2 other forms of identity that are notarized - I would think that people that jump hogwild into SSO will want an identity provider they choose to also trust them - it&#039;s impossible for wordpress personnel to establish that sort of trust in/with me).

It&#039;s great that wordpress offers the option for outbound logins, but unless they also accept OpenIds from other providers for login into their services they are not really &quot;open&quot;.  Sort of like a one-way fishtrap if you ask me.

I sincerely hope that wordpress continues to grow,  I like their blog service.  I also hope that Wordpress will build up a significant OpenID base for the users which choose to use them for that service. 

A good way for that viability to develop is to support open standards fully, meaning they should accept OpenIDs from other trust providers into their own site as well.   If they do, my guess is they will be more successfull at developing their own OpenID service, not less successful.</description>
		<content:encoded><![CDATA[<p>It&#8217;s nice that WordPress offers OpenIDs to its users, but not everyone will want to be forced to use WordPress as their exclusive OpenID provider.  The Microsoft passport example is a good one, and people should remember that and heed it well.</p>
<p>Beyond the most important factor, Trust, there are many reasons for this:  logisitcs (someone already has an OpenID elsewhere), strenght of authentication (someone has an OpenID provider that offers very strong Identity protection for them at login &#8211; such as a biometric,e tc.), long term viability of wordpress as a site or IdP (people need to know that they will have longterm and full control of their own Identities), and inverse trust &#8212; someone I choose to trust also trusting and vetting me before establishing my identity with them (you can&#8217;t get a passport for example, without 2 other forms of identity that are notarized &#8211; I would think that people that jump hogwild into SSO will want an identity provider they choose to also trust them &#8211; it&#8217;s impossible for wordpress personnel to establish that sort of trust in/with me).</p>
<p>It&#8217;s great that wordpress offers the option for outbound logins, but unless they also accept OpenIds from other providers for login into their services they are not really &#8220;open&#8221;.  Sort of like a one-way fishtrap if you ask me.</p>
<p>I sincerely hope that wordpress continues to grow,  I like their blog service.  I also hope that WordPress will build up a significant OpenID base for the users which choose to use them for that service. </p>
<p>A good way for that viability to develop is to support open standards fully, meaning they should accept OpenIDs from other trust providers into their own site as well.   If they do, my guess is they will be more successfull at developing their own OpenID service, not less successful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gnoletcom</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-126</link>
		<dc:creator>Gnoletcom</dc:creator>
		<pubDate>Fri, 13 Apr 2007 21:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-126</guid>
		<description>Please join for discussions on topics about The Virtual Reality. 
Technology development of The Virtual Reality and its perspectives. 
&lt;a href=&quot;http://gnolet.com/&quot; rel=&quot;nofollow&quot;&gt;Gnolet.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Please join for discussions on topics about The Virtual Reality.<br />
Technology development of The Virtual Reality and its perspectives.<br />
<a href="http://gnolet.com/" rel="nofollow">Gnolet.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan B</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-38</link>
		<dc:creator>Ryan B</dc:creator>
		<pubDate>Sun, 18 Mar 2007 03:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-38</guid>
		<description>Yeah I would&#039;ve liked them to integrate them with other hosts. I opened up a myOpenID.com account the other day...</description>
		<content:encoded><![CDATA[<p>Yeah I would&#8217;ve liked them to integrate them with other hosts. I opened up a myOpenID.com account the other day&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress and OpenID, the Week After &#171; Changing Way</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-29</link>
		<dc:creator>WordPress and OpenID, the Week After &#171; Changing Way</dc:creator>
		<pubDate>Mon, 12 Mar 2007 21:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-29</guid>
		<description>[...] being an OpenID provider, but not (yet?) an OpenID consumer, goes on. We can see (here and here, for example) the conversation turning to the question of whether a site should be a provider [...]</description>
		<content:encoded><![CDATA[<p>[...] being an OpenID provider, but not (yet?) an OpenID consumer, goes on. We can see (here and here, for example) the conversation turning to the question of whether a site should be a provider [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: options</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-26</link>
		<dc:creator>options</dc:creator>
		<pubDate>Sat, 10 Mar 2007 23:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-26</guid>
		<description>considering a fact that &lt;a href=&quot;http://changingway.org/2007/03/06/wordpresscom-produces-openids/#comment-52&quot; rel=&quot;nofollow&quot;&gt;Matt is still wondering&lt;/a&gt; about: &quot;What problems we’re having do you think accepting OpenIDs would solve?&quot;, I&#039;ve got a strong doubt about &lt;em&gt;eventual&lt;/em&gt; support of RP on .COM</description>
		<content:encoded><![CDATA[<p>considering a fact that <a href="http://changingway.org/2007/03/06/wordpresscom-produces-openids/#comment-52" rel="nofollow">Matt is still wondering</a> about: &#8220;What problems we’re having do you think accepting OpenIDs would solve?&#8221;, I&#8217;ve got a strong doubt about <em>eventual</em> support of RP on .COM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VxJasonxV</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-25</link>
		<dc:creator>VxJasonxV</dc:creator>
		<pubDate>Sat, 10 Mar 2007 23:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-25</guid>
		<description>Yes, there are two sides to support.
So far as I understand it, consumer support is coming eventually. Something like that, considering how Wordpress&#039; user account scheme works, takes a little bit more work to support.

But for now, go sign into Jyte, or Zooomr, or some other OpenID Enabled site with your Wordpress ID, and have fun!</description>
		<content:encoded><![CDATA[<p>Yes, there are two sides to support.<br />
So far as I understand it, consumer support is coming eventually. Something like that, considering how WordPress&#8217; user account scheme works, takes a little bit more work to support.</p>
<p>But for now, go sign into Jyte, or Zooomr, or some other OpenID Enabled site with your WordPress ID, and have fun!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Should public Web services be OpenID providers only? &#171; JAWW (beta)</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-24</link>
		<dc:creator>Should public Web services be OpenID providers only? &#171; JAWW (beta)</dc:creator>
		<pubDate>Sat, 10 Mar 2007 22:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-24</guid>
		<description>[...] &#8212; options @ 22:44   this is a slightly paraphrased question initially posed on the &#8220;Web &amp; Web Usability&#8221; weblog by Diego Ferreyra: Imagine every service (any service) provider did that. Blogger, [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8212; options @ 22:44   this is a slightly paraphrased question initially posed on the &#8220;Web &amp; Web Usability&#8221; weblog by Diego Ferreyra: Imagine every service (any service) provider did that. Blogger, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego Ferreyra</title>
		<link>http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-22</link>
		<dc:creator>Diego Ferreyra</dc:creator>
		<pubDate>Fri, 09 Mar 2007 18:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://webwebusability.wordpress.com/2007/03/07/wordpress-openid-not-really/#comment-22</guid>
		<description>That&#039;s not the point. They can create all the useless OpenID they want. The point here is claiming support of a technology that&#039;s supossed to solve a problem when the actual *support* they have doesn&#039;t help solving the problem.

I wonder what people would&#039;ve said if it was Microsoft who had given this kind of OpenID support. &quot;Now you can use yourname.passport.com as an OpenID account&quot; - &quot;No, you can&#039;t sign in into our services using another&#039;s provider OpenID&quot;.</description>
		<content:encoded><![CDATA[<p>That&#8217;s not the point. They can create all the useless OpenID they want. The point here is claiming support of a technology that&#8217;s supossed to solve a problem when the actual *support* they have doesn&#8217;t help solving the problem.</p>
<p>I wonder what people would&#8217;ve said if it was Microsoft who had given this kind of OpenID support. &#8220;Now you can use yourname.passport.com as an OpenID account&#8221; &#8211; &#8220;No, you can&#8217;t sign in into our services using another&#8217;s provider OpenID&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
