<?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: Researching Google&#8217;s Moves in OpenID</title>
	<atom:link href="http://marshallk.com/googles-moves-in-openid-no-small-matter/feed" rel="self" type="application/rss+xml" />
	<link>http://marshallk.com/googles-moves-in-openid-no-small-matter</link>
	<description></description>
	<lastBuildDate>Thu, 17 May 2012 07:27:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Pete</title>
		<link>http://marshallk.com/googles-moves-in-openid-no-small-matter/comment-page-1#comment-115750</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Mon, 13 Jul 2009 17:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://marshallk.com/?p=577#comment-115750</guid>
		<description>As a lawyer who helps people recover from identity theft, Google offering OpenID provider functionality raises privacy, identity theft, and legal concerns. In the event that the OpenID username and password database&#039;s security is compromised, a staggering amount of personal, private, and confidential information could end up in the wrong hands. OpenID is great for social bookmarking and posting; however,  I would not recommend its use for banking, financial, medical or business use. I hope this helps, because this topic certainly deserves further investigation.</description>
		<content:encoded><![CDATA[<p>As a lawyer who helps people recover from identity theft, Google offering OpenID provider functionality raises privacy, identity theft, and legal concerns. In the event that the OpenID username and password database&#8217;s security is compromised, a staggering amount of personal, private, and confidential information could end up in the wrong hands. OpenID is great for social bookmarking and posting; however,  I would not recommend its use for banking, financial, medical or business use. I hope this helps, because this topic certainly deserves further investigation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy Post</title>
		<link>http://marshallk.com/googles-moves-in-openid-no-small-matter/comment-page-1#comment-114286</link>
		<dc:creator>Timothy Post</dc:creator>
		<pubDate>Thu, 09 Jul 2009 12:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://marshallk.com/?p=577#comment-114286</guid>
		<description>The missing piece in the OpenID puzzle is for users to have the ability to validate, through DNS validation, a SUB-DOMAIN. 

There&#039;s two benefits to OpenID. The first, and most widely known, is the ability to have a single universal username for all your web logins. While this use of OpenID is fine it is not really that unique nor exciting.

The second benefit is the ability to use your OpenID validated domain as a central social hub for all your web activity. The current group of providers makes people use a sub-domain linked to their own domains (e.g. marshall.myopenid.com. This requirement effectively locks you into that OpenID providers and makes it very difficult to migrate.

The reason I am hopeful about Google Apps being an OpenID provider is that it already let&#039;s users set-up custom sub-domains by creating a new CNAME in your DNS settings.

If google let&#039;s users do the same with their OpenID domains then this is indeed a game changer.

I would recommend that Google take it one step further and let users create two sub-domains associated with their validated OpenID accounts- one for logins (login.marshallk.com) and another as their social hubs, lifestream.marshallk.com.

If we really want to push the envelope then we should also suggest that Google link one&#039;s OpenID account with one&#039;s Google Profile account.

Great to see Google push the OpenID community forward since it&#039;s been stuck for a while now.</description>
		<content:encoded><![CDATA[<p>The missing piece in the OpenID puzzle is for users to have the ability to validate, through DNS validation, a SUB-DOMAIN. </p>
<p>There&#8217;s two benefits to OpenID. The first, and most widely known, is the ability to have a single universal username for all your web logins. While this use of OpenID is fine it is not really that unique nor exciting.</p>
<p>The second benefit is the ability to use your OpenID validated domain as a central social hub for all your web activity. The current group of providers makes people use a sub-domain linked to their own domains (e.g. marshall.myopenid.com. This requirement effectively locks you into that OpenID providers and makes it very difficult to migrate.</p>
<p>The reason I am hopeful about Google Apps being an OpenID provider is that it already let&#8217;s users set-up custom sub-domains by creating a new CNAME in your DNS settings.</p>
<p>If google let&#8217;s users do the same with their OpenID domains then this is indeed a game changer.</p>
<p>I would recommend that Google take it one step further and let users create two sub-domains associated with their validated OpenID accounts- one for logins (login.marshallk.com) and another as their social hubs, lifestream.marshallk.com.</p>
<p>If we really want to push the envelope then we should also suggest that Google link one&#8217;s OpenID account with one&#8217;s Google Profile account.</p>
<p>Great to see Google push the OpenID community forward since it&#8217;s been stuck for a while now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

