<?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: OpenId</title>
	<atom:link href="http://www.programmersparadox.com/2008/04/22/openid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.programmersparadox.com/2008/04/22/openid/</link>
	<description></description>
	<lastBuildDate>Thu, 19 Jan 2012 13:42:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Luke Hoersten</title>
		<link>http://www.programmersparadox.com/2008/04/22/openid/comment-page-1/#comment-325</link>
		<dc:creator>Luke Hoersten</dc:creator>
		<pubDate>Tue, 29 Apr 2008 01:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/?p=96#comment-325</guid>
		<description>Yeah good point. I thought just the metadata linking in the page (the process I posted) was also very hard to find and figure out, even though it&#039;s easy once you see how it&#039;s supposed to be. They definitely don&#039;t seem to be trying for usability, do they?</description>
		<content:encoded><![CDATA[<p>Yeah good point. I thought just the metadata linking in the page (the process I posted) was also very hard to find and figure out, even though it&#8217;s easy once you see how it&#8217;s supposed to be. They definitely don&#8217;t seem to be trying for usability, do they?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.programmersparadox.com/2008/04/22/openid/comment-page-1/#comment-324</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 29 Apr 2008 01:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/?p=96#comment-324</guid>
		<description>I&#039;m not sure exactly what I was expecting.  Certainly not anything different than what I found.  While I&#039;m not planning at the current time to use my domain to link to a bunch of openid accounts, I still thought it would be cool to set it up so that my openid pointed to my domain.  For a single account it might have been easier just to link to myOpenID or some other provider.  Certainly that is what users will have to do if they can&#039;t modify their DNS.

My biggest complaint isn&#039;t with the end result or that I even potentially set up more than I needed.  It is that myOpenID does not make the process clear.  Point 2 in the email from Mike Glover is: your signin on myopenid.com is the same as your identifier.  Nowhere did I see that on the myOpenID site, so I fumbled in the dark until I figured it out on my own.  It&#039;s the small things like that that myOpenID needs to fix.

Once they do that, it should be a great service.  I just thought I&#039;d point out what I saw as the faults now so that maybe myOpenID will read them and get better and so that others who want to try the process can learn from what I went through.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure exactly what I was expecting.  Certainly not anything different than what I found.  While I&#8217;m not planning at the current time to use my domain to link to a bunch of openid accounts, I still thought it would be cool to set it up so that my openid pointed to my domain.  For a single account it might have been easier just to link to myOpenID or some other provider.  Certainly that is what users will have to do if they can&#8217;t modify their DNS.</p>
<p>My biggest complaint isn&#8217;t with the end result or that I even potentially set up more than I needed.  It is that myOpenID does not make the process clear.  Point 2 in the email from Mike Glover is: your signin on myopenid.com is the same as your identifier.  Nowhere did I see that on the myOpenID site, so I fumbled in the dark until I figured it out on my own.  It&#8217;s the small things like that that myOpenID needs to fix.</p>
<p>Once they do that, it should be a great service.  I just thought I&#8217;d point out what I saw as the faults now so that maybe myOpenID will read them and get better and so that others who want to try the process can learn from what I went through.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Hoersten</title>
		<link>http://www.programmersparadox.com/2008/04/22/openid/comment-page-1/#comment-320</link>
		<dc:creator>Luke Hoersten</dc:creator>
		<pubDate>Sun, 27 Apr 2008 01:31:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/?p=96#comment-320</guid>
		<description>I think you are using the wrong feature for the job for your domain. What you&#039;ve set up is the equivalent to Google Apps and a domain. A way to give all the users of your domain an OpenID. In that sense, myOpenID&#039;s acted exactly as I&#039;d expect (and the way Google Apps works).

myOpenID, in your defense, does &lt;em&gt;not&lt;/em&gt; make this clear at all! I emailed them when they first released this because I felt like they were misleading users into this more complex setup. Here&#039;s an email explanation from Mike Glover, myOpenID support:
&lt;blockquote&gt;&quot;myOpenID for Domains is intended for small or medium-sized groups of people that want an easy way to set up branded OpenIDs for their entire group.  It has two advantages over adding openid.server to your metadata:

  1. Easier setup, especially if you&#039;re setting up a lot of accounts
  2. Your signin on myopenid.com is the same as your identifier

For just setting up one or two accounts on your domain, it&#039;s probably more trouble than it&#039;s worth.  We&#039;ll be adding some more information to the site about choosing the best method to use your domain with OpenID soon.&quot;&lt;/blockquote&gt;

I wrote a guide a while ago to better explain how I set up all my stuff. I use Google Apps for most of it. To be more canonical, the way you&#039;ve set it up is better anyway.

&lt;a href=&quot;http://humani.st/unified-web-persona-custom-openid-g-talk-urls/&quot; rel=&quot;nofollow&quot;&gt;Unified Web Persona: Custom OpenID &amp; G-Talk URLs&lt;/a&gt;

Let me know if this fits more with what you were initially expecting.

-Luke</description>
		<content:encoded><![CDATA[<p>I think you are using the wrong feature for the job for your domain. What you&#8217;ve set up is the equivalent to Google Apps and a domain. A way to give all the users of your domain an OpenID. In that sense, myOpenID&#8217;s acted exactly as I&#8217;d expect (and the way Google Apps works).</p>
<p>myOpenID, in your defense, does <em>not</em> make this clear at all! I emailed them when they first released this because I felt like they were misleading users into this more complex setup. Here&#8217;s an email explanation from Mike Glover, myOpenID support:</p>
<blockquote><p>&#8220;myOpenID for Domains is intended for small or medium-sized groups of people that want an easy way to set up branded OpenIDs for their entire group.  It has two advantages over adding openid.server to your metadata:</p>
<p>  1. Easier setup, especially if you&#8217;re setting up a lot of accounts<br />
  2. Your signin on myopenid.com is the same as your identifier</p>
<p>For just setting up one or two accounts on your domain, it&#8217;s probably more trouble than it&#8217;s worth.  We&#8217;ll be adding some more information to the site about choosing the best method to use your domain with OpenID soon.&#8221;</p></blockquote>
<p>I wrote a guide a while ago to better explain how I set up all my stuff. I use Google Apps for most of it. To be more canonical, the way you&#8217;ve set it up is better anyway.</p>
<p><a href="http://humani.st/unified-web-persona-custom-openid-g-talk-urls/" rel="nofollow">Unified Web Persona: Custom OpenID &amp; G-Talk URLs</a></p>
<p>Let me know if this fits more with what you were initially expecting.</p>
<p>-Luke</p>
]]></content:encoded>
	</item>
</channel>
</rss>

