<?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"
	>
<channel>
	<title>Comments on: Privacy and Data Ownership Do Not Apply</title>
	<atom:link href="http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/feed/" rel="self" type="application/rss+xml" />
	<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/</link>
	<description>Where programming, the internet and social media collide.</description>
	<pubDate>Thu, 21 Aug 2008 21:37:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: admin</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-233</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 16 May 2008 18:45:07 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-233</guid>
		<description>@Kevin
Interesting analogy with IMs. There is only limited interoperability by publishing APIs. XMPP is meant to provide true interop, but there does not seem to be a ton of support. However, I do not follow IM technology at that detail anymore.</description>
		<content:encoded><![CDATA[<p>@Kevin<br />
Interesting analogy with IMs. There is only limited interoperability by publishing APIs. XMPP is meant to provide true interop, but there does not seem to be a ton of support. However, I do not follow IM technology at that detail anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Heisler</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-232</link>
		<dc:creator>Kevin Heisler</dc:creator>
		<pubDate>Fri, 16 May 2008 18:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-232</guid>
		<description>This reminds me of the early battles over IM before Trillian and others enabled some degree of interoperability. It's clear that Facebook wants to keep their members inside their garden walls. 

Facebook is building a moat around its castle to keep the search giant out.


Dear Google, Facebook's Just Not That Into You
http://blog.searchenginewatch.com/blog/080516-110559</description>
		<content:encoded><![CDATA[<p>This reminds me of the early battles over IM before Trillian and others enabled some degree of interoperability. It&#8217;s clear that Facebook wants to keep their members inside their garden walls. </p>
<p>Facebook is building a moat around its castle to keep the search giant out.</p>
<p>Dear Google, Facebook&#8217;s Just Not That Into You<br />
<a href="http://blog.searchenginewatch.com/blog/080516-110559" rel="nofollow">http://blog.searchenginewatch......516-110559</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-231</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 16 May 2008 14:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-231</guid>
		<description>@Ben
I commented on your blog regarding openid and oauth. Definitely the right way to go.

@rloughery
By paying someone, you are hopefully getting the ability to enforce the terms of service and privacy policy. The commercial service allows you to expect certain things, but it is also the nature of supply and demand that allow companies to charge for certain services. Granted there should be some level of data backup, but that may not be guaranteed.</description>
		<content:encoded><![CDATA[<p>@Ben<br />
I commented on your blog regarding openid and oauth. Definitely the right way to go.</p>
<p>@rloughery<br />
By paying someone, you are hopefully getting the ability to enforce the terms of service and privacy policy. The commercial service allows you to expect certain things, but it is also the nature of supply and demand that allow companies to charge for certain services. Granted there should be some level of data backup, but that may not be guaranteed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rloughery</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-230</link>
		<dc:creator>rloughery</dc:creator>
		<pubDate>Fri, 16 May 2008 14:03:16 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-230</guid>
		<description>The only point that I would add... is that if you pay to store your data on a site, i.e. using Yahoo to host your work email domain, etc. Than shouldn't we be able to expect that by paying Yahoo (or Google) we are trusting them not do anything with our data but to make sure it is safe and backed up??</description>
		<content:encoded><![CDATA[<p>The only point that I would add&#8230; is that if you pay to store your data on a site, i.e. using Yahoo to host your work email domain, etc. Than shouldn&#8217;t we be able to expect that by paying Yahoo (or Google) we are trusting them not do anything with our data but to make sure it is safe and backed up??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Clemens</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-229</link>
		<dc:creator>Ben Clemens</dc:creator>
		<pubDate>Fri, 16 May 2008 13:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-229</guid>
		<description>Great post... I have a take on this as well: http://www.practicalist.com/mt/archives/000477.html

"An alternate solution would be to allow people to own their personal information store, and choose to allow social network sites access to this store. Sites that behaved badly could be banned. This is much like OpenID and Oauth in concept, where one's identity is tied to a DNS-like way of creating a single namespace for unique user identifiers. It could take the form of a fancier version of an "Attention Profile Markup Language" file; a "Social Profile Markup Language" file, say. It would be stored on my own web server and under my direct control. If I wanted to share with Friendfeed or mybloglog (for example) what sites I've been posting to, saving, liking, or reading, I could allow them to access my SPML file under the condition that it be removed if I decided not to use the application any longer. (This is a geeky solution, but that's usually where these things start.) There should be a better solution to the new portability of social data than exists today, or my own understanding of my personal information will mean less and less."</description>
		<content:encoded><![CDATA[<p>Great post&#8230; I have a take on this as well: <a href="http://www.practicalist.com/mt/archives/000477.html" rel="nofollow">http://www.practicalist.com/mt.....00477.html</a></p>
<p>&#8220;An alternate solution would be to allow people to own their personal information store, and choose to allow social network sites access to this store. Sites that behaved badly could be banned. This is much like OpenID and Oauth in concept, where one&#8217;s identity is tied to a DNS-like way of creating a single namespace for unique user identifiers. It could take the form of a fancier version of an &#8220;Attention Profile Markup Language&#8221; file; a &#8220;Social Profile Markup Language&#8221; file, say. It would be stored on my own web server and under my direct control. If I wanted to share with Friendfeed or mybloglog (for example) what sites I&#8217;ve been posting to, saving, liking, or reading, I could allow them to access my SPML file under the condition that it be removed if I decided not to use the application any longer. (This is a geeky solution, but that&#8217;s usually where these things start.) There should be a better solution to the new portability of social data than exists today, or my own understanding of my personal information will mean less and less.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Privacy and Data Ownership Do Not Apply &#124; My Geek Solutions</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-228</link>
		<dc:creator>Privacy and Data Ownership Do Not Apply &#124; My Geek Solutions</dc:creator>
		<pubDate>Fri, 16 May 2008 12:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-228</guid>
		<description>[...] admin wrote an interesting post today onHere&#8217;s a quick excerptGiven the recent block of Google Friend Connect by Facebook, TechCrunch and Robert Scoble decided to start an argument. This is perfect fodder for this week’s bitchmeme as there are a few issues that people tend to ignore. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] admin wrote an interesting post today onHere&#8217;s a quick excerptGiven the recent block of Google Friend Connect by Facebook, TechCrunch and Robert Scoble decided to start an argument. This is perfect fodder for this week’s bitchmeme as there are a few issues that people tend to ignore. &#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Facebook &#187; Privacy and Data Ownership Do Not Apply</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-227</link>
		<dc:creator>Facebook &#187; Privacy and Data Ownership Do Not Apply</dc:creator>
		<pubDate>Fri, 16 May 2008 12:20:46 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-227</guid>
		<description>[...] admin wrote an interesting post today on Privacy and Data Ownership Do Not ApplyHere&#8217;s a quick excerptGiven the recent block of Google Friend Connect by Facebook, TechCrunch and Robert Scoble decided to start an argument. This is perfect fodder for this week’s bitchmeme as there are a few issues that people tend to ignore. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] admin wrote an interesting post today on Privacy and Data Ownership Do Not ApplyHere&#8217;s a quick excerptGiven the recent block of Google Friend Connect by Facebook, TechCrunch and Robert Scoble decided to start an argument. This is perfect fodder for this week’s bitchmeme as there are a few issues that people tend to ignore. &#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-226</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 16 May 2008 10:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-226</guid>
		<description>@Colin
That is the reason we keep seeing data portability announcements. Everyone knows they need to support it in order to stay competitive. The problem is that data portability still needs some work, specifically synchronization and privacy.

We will get there, it will just take time.</description>
		<content:encoded><![CDATA[<p>@Colin<br />
That is the reason we keep seeing data portability announcements. Everyone knows they need to support it in order to stay competitive. The problem is that data portability still needs some work, specifically synchronization and privacy.</p>
<p>We will get there, it will just take time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Walker</title>
		<link>http://regulargeek.com/2008/05/16/privacy-and-data-ownership-do-not-apply/#comment-225</link>
		<dc:creator>Colin Walker</dc:creator>
		<pubDate>Fri, 16 May 2008 10:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://regulargeek.com/?p=54#comment-225</guid>
		<description>We have become spoilt in a way with the APIs and openness of some services that it has become 'expected' that this will exist everywhere (hence the whole data portability movement) but as you rightly say, this just isn't the case.

There is an element of jump on board or get left behind, however, and it is up to each service to decide how they want to go about these things but the crux is if they don't open up - at least to a degree - then the user will migrate to someone who has.</description>
		<content:encoded><![CDATA[<p>We have become spoilt in a way with the APIs and openness of some services that it has become &#8216;expected&#8217; that this will exist everywhere (hence the whole data portability movement) but as you rightly say, this just isn&#8217;t the case.</p>
<p>There is an element of jump on board or get left behind, however, and it is up to each service to decide how they want to go about these things but the crux is if they don&#8217;t open up - at least to a degree - then the user will migrate to someone who has.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
