<?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: Protecting your privacy when moving data between social networks</title>
	<atom:link href="http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks</link>
	<description>Digital Lifestyle Aggregation - helping to establish open source infrastructure</description>
	<pubDate>Sat, 30 Aug 2008 02:28:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Vlad</title>
		<link>http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-90557</link>
		<dc:creator>Vlad</dc:creator>
		<pubDate>Sat, 02 Sep 2006 11:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-90557</guid>
		<description>OpenID is just an identity system - to make single sign-on easier. It's not about trust or managing your private infromation. There is an extension, but it's not primary purpose</description>
		<content:encoded><![CDATA[<p>OpenID is just an identity system - to make single sign-on easier. It&#8217;s not about trust or managing your private infromation. There is an extension, but it&#8217;s not primary purpose</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raju</title>
		<link>http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-62334</link>
		<dc:creator>Raju</dc:creator>
		<pubDate>Mon, 17 Jul 2006 17:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-62334</guid>
		<description>Martin, that sounds good. Let's look at the way we deal with personal information outside the web: White pages, Yellow pages, etc. Lists of names (people, companies, institutions) linking the name to an information structure we know how to use: the address. So we don't need 100 white pages but one central repository for this information.</description>
		<content:encoded><![CDATA[<p>Martin, that sounds good. Let&#8217;s look at the way we deal with personal information outside the web: White pages, Yellow pages, etc. Lists of names (people, companies, institutions) linking the name to an information structure we know how to use: the address. So we don&#8217;t need 100 white pages but one central repository for this information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Spernau</title>
		<link>http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-62111</link>
		<dc:creator>Martin Spernau</dc:creator>
		<pubDate>Mon, 17 Jul 2006 02:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-62111</guid>
		<description>Maybe a more radicat vision: What if we assume a sort og Meta-SNS. Where people do not NEED to move along with the network to continue to take part in it?

So, Joe has this group on Yahoo!, and wants to move it to PA. The big idea/vision of PA is (as I understand it) that people can be a member of any SNS to participate in a PA group/network/whatever. So Joe's friends can stay whereever they are now, and still take part in his new network...

Sure, this is (only) a vision, that needs to be expressed in code and processes somehow, but idealy no one needs to be a member of PA to participate in a group/network there, right?

Maybe the fiends-list Joe brings along can be a simple list od pointers. Each friend-entry is a pointer to the profile of that user - whereever that may be. The OpenID idedtifier URLs are pretty much that. An URL pointing to your profilepage at the network that hosts it. Or your own, if you have control.

-Martin</description>
		<content:encoded><![CDATA[<p>Maybe a more radicat vision: What if we assume a sort og Meta-SNS. Where people do not NEED to move along with the network to continue to take part in it?</p>
<p>So, Joe has this group on Yahoo!, and wants to move it to PA. The big idea/vision of PA is (as I understand it) that people can be a member of any SNS to participate in a PA group/network/whatever. So Joe&#8217;s friends can stay whereever they are now, and still take part in his new network&#8230;</p>
<p>Sure, this is (only) a vision, that needs to be expressed in code and processes somehow, but idealy no one needs to be a member of PA to participate in a group/network there, right?</p>
<p>Maybe the fiends-list Joe brings along can be a simple list od pointers. Each friend-entry is a pointer to the profile of that user - whereever that may be. The OpenID idedtifier URLs are pretty much that. An URL pointing to your profilepage at the network that hosts it. Or your own, if you have control.</p>
<p>-Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Arnett</title>
		<link>http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-61979</link>
		<dc:creator>Nick Arnett</dc:creator>
		<pubDate>Sun, 16 Jul 2006 21:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2006/07/protesting-your-privacy-when-moving-data-between-social-networks#comment-61979</guid>
		<description>Another possibility... create a new, pseudonymous, identity for the friends on the destination website... give them the option of linking that identity to their others.  I think the open source community could provide leadership for standards that allow people to prove that they own an on-line identity with minimal information disclosure.

To make this perhaps a little clearer... Joe takes his network to a new place and says that he has 150 friends.  For each friend, Joe gets back a token that he can send to his friends... the token will prove to the new site that the person using it really is Joe's friend.  Thus, Joe reveals nothing about his friends and it's up to Joe to decide if he wants to send the tokens.  When a friend receives a token but already has a membership at the new site, the token will simple allow him to "merge" the two identities ("Joe's friend" and their own) on the new site.

And hey, Marc... long time!  Can't remember when we last saw each other... but I've spent the last 10 years working on social networking of one sort or another, mostly focused on analysis of communties.

Nick</description>
		<content:encoded><![CDATA[<p>Another possibility&#8230; create a new, pseudonymous, identity for the friends on the destination website&#8230; give them the option of linking that identity to their others.  I think the open source community could provide leadership for standards that allow people to prove that they own an on-line identity with minimal information disclosure.</p>
<p>To make this perhaps a little clearer&#8230; Joe takes his network to a new place and says that he has 150 friends.  For each friend, Joe gets back a token that he can send to his friends&#8230; the token will prove to the new site that the person using it really is Joe&#8217;s friend.  Thus, Joe reveals nothing about his friends and it&#8217;s up to Joe to decide if he wants to send the tokens.  When a friend receives a token but already has a membership at the new site, the token will simple allow him to &#8220;merge&#8221; the two identities (&#8221;Joe&#8217;s friend&#8221; and their own) on the new site.</p>
<p>And hey, Marc&#8230; long time!  Can&#8217;t remember when we last saw each other&#8230; but I&#8217;ve spent the last 10 years working on social networking of one sort or another, mostly focused on analysis of communties.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
</channel>
</rss>
