<?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: Announcing Emailtoid: mapping email addresses to OpenIDs</title>
	<atom:link href="http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<lastBuildDate>Fri, 19 Mar 2010 18:39:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: OpenID usability is not an oxymoron &#124; FactoryCity</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-103460</link>
		<dc:creator>OpenID usability is not an oxymoron &#124; FactoryCity</dc:creator>
		<pubDate>Sun, 04 Jan 2009 20:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-103460</guid>
		<description>[...] is my opinion that enabling an email address to be used as a &#8220;hint&#8221; that resolves to a valid OpenID URL is a necessary step to dislodge one of the main nettles [...]</description>
		<content:encoded><![CDATA[<p>[...] is my opinion that enabling an email address to be used as a &#8220;hint&#8221; that resolves to a valid OpenID URL is a necessary step to dislodge one of the main nettles [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Independent study on OpenID awareness using Mechanical Turk &#124; FactoryCity</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-102895</link>
		<dc:creator>Independent study on OpenID awareness using Mechanical Turk &#124; FactoryCity</dc:creator>
		<pubDate>Thu, 13 Nov 2008 05:42:45 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-102895</guid>
		<description>[...] also that momentum to rev the protocol to accommodate email addresses in OpenID is just now gaining [...]</description>
		<content:encoded><![CDATA[<p>[...] also that momentum to rev the protocol to accommodate email addresses in OpenID is just now gaining [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vincent</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-102842</link>
		<dc:creator>Vincent</dc:creator>
		<pubDate>Sat, 08 Nov 2008 21:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-102842</guid>
		<description>It does sound like an interesting idea, provided that, instead of redirecting the user to emailtoid, you send an email out to the user yourself and provide him with an OpenID based on a code in that email.</description>
		<content:encoded><![CDATA[<p>It does sound like an interesting idea, provided that, instead of redirecting the user to emailtoid, you send an email out to the user yourself and provide him with an OpenID based on a code in that email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenID per E-Mail at notizBlog - a private weblog written by Matthias Pfefferle</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99566</link>
		<dc:creator>OpenID per E-Mail at notizBlog - a private weblog written by Matthias Pfefferle</dc:creator>
		<pubDate>Thu, 03 Jul 2008 18:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99566</guid>
		<description>[...] (via)           &#171; Wie viel Portabilitiy brauchen wir noch? [...]</description>
		<content:encoded><![CDATA[<p>[...] (via)           &laquo; Wie viel Portabilitiy brauchen wir noch? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Messaging</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99447</link>
		<dc:creator>Enterprise Messaging</dc:creator>
		<pubDate>Fri, 27 Jun 2008 11:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99447</guid>
		<description>Sounds like an interesting service.</description>
		<content:encoded><![CDATA[<p>Sounds like an interesting service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99441</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Wed, 25 Jun 2008 14:47:44 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99441</guid>
		<description>@Pascal: Well, that&#039;s a huge problem actually -- that&#039;s like having competing DNS providers! Again, ideally the email providers will adopt the discovery solution -- or will themselves delegate/redirect to a third-party OpenID provider. Having multiple email-to-OpenID mappers would actually be pretty bad and one of the reasons why Emailtoid is potentially problematic as a privately-run project...

However, it pushes the idea out there and forces us to confront any potential technical issues with using email addresses as OpenIDs. AFAIC in that case, it&#039;s a useful exercise and service until email providers get hip to providing identity on their own.</description>
		<content:encoded><![CDATA[<p>@Pascal: Well, that&#8217;s a huge problem actually &#8212; that&#8217;s like having competing DNS providers! Again, ideally the email providers will adopt the discovery solution &#8212; or will themselves delegate/redirect to a third-party OpenID provider. Having multiple email-to-OpenID mappers would actually be pretty bad and one of the reasons why Emailtoid is potentially problematic as a privately-run project&#8230;</p>
<p>However, it pushes the idea out there and forces us to confront any potential technical issues with using email addresses as OpenIDs. AFAIC in that case, it&#8217;s a useful exercise and service until email providers get hip to providing identity on their own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pascal Van Hecke</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99440</link>
		<dc:creator>Pascal Van Hecke</dc:creator>
		<pubDate>Wed, 25 Jun 2008 12:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99440</guid>
		<description>If this idea catches on, existing openid providers will compete for relying parties to choose them (i.e. the openid providers) as fallback service...  probably by including it in an affiliate program (such as the one that myopenid already has in place).</description>
		<content:encoded><![CDATA[<p>If this idea catches on, existing openid providers will compete for relying parties to choose them (i.e. the openid providers) as fallback service&#8230;  probably by including it in an affiliate program (such as the one that myopenid already has in place).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99430</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Mon, 23 Jun 2008 17:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99430</guid>
		<description>@Stephen: AFAIK, the OpenID spec forbids using http://user@example.com as a valid OpenID, so this doesn&#039;t change anything.</description>
		<content:encoded><![CDATA[<p>@Stephen: AFAIK, the OpenID spec forbids using <a href="http://user@example.com" rel="nofollow">http://user@example.com</a> as a valid OpenID, so this doesn&#8217;t change anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Paul Weber</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99428</link>
		<dc:creator>Stephen Paul Weber</dc:creator>
		<pubDate>Mon, 23 Jun 2008 14:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99428</guid>
		<description>Biggest issue I have with this is that currently:

user@example.com

get&#039;s mapped to

http://user@example.com/

Which is a valid URL and may in fact be their OpenID.  This re-mapping idea changes this a lot.</description>
		<content:encoded><![CDATA[<p>Biggest issue I have with this is that currently:</p>
<p><a href="mailto:user@example.com">user@example.com</a></p>
<p>get&#8217;s mapped to</p>
<p><a href="http://user@example.com/" rel="nofollow">http://user@example.com/</a></p>
<p>Which is a valid URL and may in fact be their OpenID.  This re-mapping idea changes this a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-06-23 &#171; Breyten&#8217;s Dev Blog</title>
		<link>http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/comment-page-1/#comment-99426</link>
		<dc:creator>links for 2008-06-23 &#171; Breyten&#8217;s Dev Blog</dc:creator>
		<pubDate>Mon, 23 Jun 2008 11:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=961#comment-99426</guid>
		<description>[...] Announcing Emailtoid: mapping email addresses to OpenIDs (tags: citizen-centric web digital identity technology usability building emailtoid openid) [...]</description>
		<content:encoded><![CDATA[<p>[...] Announcing Emailtoid: mapping email addresses to OpenIDs (tags: citizen-centric web digital identity technology usability building emailtoid openid) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
