<?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: Google Removes OpenID Whitelist Requirement</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/10/31/google-removes-openid-whitelist-requirement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/10/31/google-removes-openid-whitelist-requirement/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 08 Nov 2009 18:39:36 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kevin Yank</title>
		<link>http://www.sitepoint.com/blogs/2008/10/31/google-removes-openid-whitelist-requirement/comment-page-1/#comment-818636</link>
		<dc:creator>Kevin Yank</dc:creator>
		<pubDate>Fri, 31 Oct 2008 00:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3146#comment-818636</guid>
		<description>I’m relieved that Google is backing off its modifications to OpenID, but I agree: I won’t take their OpenID support seriously until they become a relying party.

Yes, the fact that OpenID is not a solution for desktop and other non-browser clients is an issue, but other services work around this by letting you log into their Web application (with OpenID) and retrieve a password or other secret key for use in configuring a non-Web client.</description>
		<content:encoded><![CDATA[<p>I’m relieved that Google is backing off its modifications to OpenID, but I agree: I won’t take their OpenID support seriously until they become a relying party.</p>
<p>Yes, the fact that OpenID is not a solution for desktop and other non-browser clients is an issue, but other services work around this by letting you log into their Web application (with OpenID) and retrieve a password or other secret key for use in configuring a non-Web client.</p>]]></content:encoded>
	</item>
</channel>
</rss>
