<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Data Portability</title>
	<link>http://blog.enthinnai.com/2007/12/05/data-portability/</link>
	<description>Blog by EnThinnai Team Members</description>
	<pubDate>Tue, 06 Jan 2009 21:34:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Aswath</title>
		<link>http://blog.enthinnai.com/2007/12/05/data-portability/#comment-96</link>
		<author>Aswath</author>
		<pubDate>Sat, 08 Dec 2007 00:12:33 +0000</pubDate>
		<guid>http://blog.enthinnai.com/2007/12/05/data-portability/#comment-96</guid>
		<description>Chris, thanks for the clarification. It was my bad sentence construction. As you suspected, I know OAuth is not solely from Google.

I was suggesting that, an EnThinnai user can share that data with the identified friends.</description>
		<content:encoded><![CDATA[<p>Chris, thanks for the clarification. It was my bad sentence construction. As you suspected, I know OAuth is not solely from Google.</p>
<p>I was suggesting that, an EnThinnai user can share that data with the identified friends.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://blog.enthinnai.com/2007/12/05/data-portability/#comment-95</link>
		<author>Chris Messina</author>
		<pubDate>Fri, 07 Dec 2007 23:34:44 +0000</pubDate>
		<guid>http://blog.enthinnai.com/2007/12/05/data-portability/#comment-95</guid>
		<description>Just a quick clarification... in your post you make it sound like OAuth is a Google initiative, like OpenSocial. This is not accurate. While Google has been productively involved in the development of the protocol, it is not under their direct guidance, in the way that OpenSocial is.

This is important, as OAuth is a collective effort by a number of providers, including AOL, Yahoo, Flickr, Twitter, Ma.gnolia, Hueniverse and others. 

It may not have been what you meant, but that's the way it currently reads.

As for your point, I think the browser has something to do with this -- but even still, the problem really will be putting all that data to good use and efficiently accessing what you want, rather than just storing it forever.</description>
		<content:encoded><![CDATA[<p>Just a quick clarification&#8230; in your post you make it sound like OAuth is a Google initiative, like OpenSocial. This is not accurate. While Google has been productively involved in the development of the protocol, it is not under their direct guidance, in the way that OpenSocial is.</p>
<p>This is important, as OAuth is a collective effort by a number of providers, including AOL, Yahoo, Flickr, Twitter, Ma.gnolia, Hueniverse and others. </p>
<p>It may not have been what you meant, but that&#8217;s the way it currently reads.</p>
<p>As for your point, I think the browser has something to do with this &#8212; but even still, the problem really will be putting all that data to good use and efficiently accessing what you want, rather than just storing it forever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Wishon</title>
		<link>http://blog.enthinnai.com/2007/12/05/data-portability/#comment-78</link>
		<author>Bill Wishon</author>
		<pubDate>Wed, 05 Dec 2007 14:56:46 +0000</pubDate>
		<guid>http://blog.enthinnai.com/2007/12/05/data-portability/#comment-78</guid>
		<description>Hi Aswath,

I agree that local storage of important personal data is one attractive option, I'd take it one step further and suggest that as data storage gets smaller, cheaper and more ubiquitous that we might even store this data on a personal device such as a cell phone or USB drive.  That way we can have the information with us at all times in case we want to log in to our social networks while we're away from home.  These devices can adopt some form of biometric authentication to prevent access to this data by the wrong person if lost.

With the right client side integration websites and applications could ask the user's profile manager for access to certain information and you could allow or deny the request for one time, a week or until you change your mind.  Much like a personal firewall works today for managing connections to and from your machine.

Cheers,
~&#62;Bill</description>
		<content:encoded><![CDATA[<p>Hi Aswath,</p>
<p>I agree that local storage of important personal data is one attractive option, I&#8217;d take it one step further and suggest that as data storage gets smaller, cheaper and more ubiquitous that we might even store this data on a personal device such as a cell phone or USB drive.  That way we can have the information with us at all times in case we want to log in to our social networks while we&#8217;re away from home.  These devices can adopt some form of biometric authentication to prevent access to this data by the wrong person if lost.</p>
<p>With the right client side integration websites and applications could ask the user&#8217;s profile manager for access to certain information and you could allow or deny the request for one time, a week or until you change your mind.  Much like a personal firewall works today for managing connections to and from your machine.</p>
<p>Cheers,<br />
~&gt;Bill</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript"> 
_uacct = "UA-1817495-3";
urchinTracker();
</script>