<?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+ The Good, the Bad, and the Ugly</title>
	<atom:link href="http://mrblog.org/2011/07/15/google-the-good-the-bad-and-the-ugly/feed/" rel="self" type="application/rss+xml" />
	<link>http://mrblog.org/2011/07/15/google-the-good-the-bad-and-the-ugly/</link>
	<description>Mr Blog.  Very technical, or silly, sometimes absurd.</description>
	<lastBuildDate>Thu, 09 May 2013 22:35:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Google+: Too complex for the average user? &#124; comUq</title>
		<link>http://mrblog.org/2011/07/15/google-the-good-the-bad-and-the-ugly/comment-page-1/#comment-5516</link>
		<dc:creator>Google+: Too complex for the average user? &#124; comUq</dc:creator>
		<pubDate>Mon, 08 Aug 2011 07:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://mrblog.org/?p=1414#comment-5516</guid>
		<description><![CDATA[[...] articles and reviews of Google+ have consistently praised the platform’s privacy features as top-notch, but too [...]]]></description>
		<content:encoded><![CDATA[<p>[...] articles and reviews of Google+ have consistently praised the platform’s privacy features as top-notch, but too [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aswath Rao</title>
		<link>http://mrblog.org/2011/07/15/google-the-good-the-bad-and-the-ugly/comment-page-1/#comment-5505</link>
		<dc:creator>Aswath Rao</dc:creator>
		<pubDate>Sat, 16 Jul 2011 03:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://mrblog.org/?p=1414#comment-5505</guid>
		<description><![CDATA[EnThinnai shows a technical approach to solve the problem you identify in &quot;Ugly&quot; section. Apart from the obvious business reason, there are no inherent reasons for Google Plus to require a Google identity for bot the &quot;poster&quot; and the &quot;receiver&quot; of the posts. EnThinnai, which was developed some four years before uses OpenID for authenticate both the parties. It has to because it is distributed social networking application and there is no single entity that can issue identity. Accordingly, my ET server will authenticate me using my OpenID and if I do Limited share, I will identify you with your OpenID and you will access the shared data at my server after authenticating yourself under OpenID protocol.

Of course Google Plus could have done the same thing.]]></description>
		<content:encoded><![CDATA[<p>EnThinnai shows a technical approach to solve the problem you identify in &#8220;Ugly&#8221; section. Apart from the obvious business reason, there are no inherent reasons for Google Plus to require a Google identity for bot the &#8220;poster&#8221; and the &#8220;receiver&#8221; of the posts. EnThinnai, which was developed some four years before uses OpenID for authenticate both the parties. It has to because it is distributed social networking application and there is no single entity that can issue identity. Accordingly, my ET server will authenticate me using my OpenID and if I do Limited share, I will identify you with your OpenID and you will access the shared data at my server after authenticating yourself under OpenID protocol.</p>
<p>Of course Google Plus could have done the same thing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
