<?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: Privacy and revocation: two sides of the same coin – a new privacy model for the social web</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html</link>
	<description>Wireless mobility - Innovation - Digital convergence - mobile web 2.0</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:47:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Stephen James</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html/comment-page-1#comment-1356</link>
		<dc:creator>Stephen James</dc:creator>
		<pubDate>Tue, 26 Feb 2008 23:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/01/privacy_and_rev.html#comment-1356</guid>
		<description>It seems that there is a false either/or choice lingering here. Either completely closed or completely open. Even in the context of a social network, where the members are not completely vetted, I would want to have some information held close to the vest, so to speak. I see nothing wrong with getting/having to control who gets to my most personal information.
</description>
		<content:encoded><![CDATA[<p>It seems that there is a false either/or choice lingering here. Either completely closed or completely open. Even in the context of a social network, where the members are not completely vetted, I would want to have some information held close to the vest, so to speak. I see nothing wrong with getting/having to control who gets to my most personal information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajit Jaokar</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html/comment-page-1#comment-1355</link>
		<dc:creator>Ajit Jaokar</dc:creator>
		<pubDate>Thu, 07 Feb 2008 17:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/01/privacy_and_rev.html#comment-1355</guid>
		<description>Thanks Stefan. I am also following the open social networks ideas with great interest. shall blog more soon rgds Ajit
</description>
		<content:encoded><![CDATA[<p>Thanks Stefan. I am also following the open social networks ideas with great interest. shall blog more soon rgds Ajit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Weiss</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html/comment-page-1#comment-1354</link>
		<dc:creator>Stefan Weiss</dc:creator>
		<pubDate>Thu, 07 Feb 2008 16:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/01/privacy_and_rev.html#comment-1354</guid>
		<description>Good to read that the challenge of enhancing the privacy of social network users get more attention at different fronts. However, your suggestion of revocing somebody&#039;s access or viewing rights of your profile information only covers a small part of what information privacy actually requires. And in some social networks such as XING this type of setting functionality already exists. But information privacy goes way beyond that. The data portability initiatives today do not truly address privacy issues but rather only cover viewing and access rights. You can possibly revoce somebody&#039;s viewing rights to your profile but what happens to the personal data you provided to one social network once that data is exported to some application developer or is scrapped from the site by an unauthorized individual? Unless we develop new methods to attach data purpose and certain usage rights to each personal data set, we will continue to care about information privacy only on the surface. At the same time personal data in all kinds of forms is spread without any kind of control by the original owner of the data. I would be interested to discuss these issues at the WebCamp event in Ireland but I am afraid I cannot be there in person. Hope to be able to follow the discussions here.
</description>
		<content:encoded><![CDATA[<p>Good to read that the challenge of enhancing the privacy of social network users get more attention at different fronts. However, your suggestion of revocing somebody&#8217;s access or viewing rights of your profile information only covers a small part of what information privacy actually requires. And in some social networks such as XING this type of setting functionality already exists. But information privacy goes way beyond that. The data portability initiatives today do not truly address privacy issues but rather only cover viewing and access rights. You can possibly revoce somebody&#8217;s viewing rights to your profile but what happens to the personal data you provided to one social network once that data is exported to some application developer or is scrapped from the site by an unauthorized individual? Unless we develop new methods to attach data purpose and certain usage rights to each personal data set, we will continue to care about information privacy only on the surface. At the same time personal data in all kinds of forms is spread without any kind of control by the original owner of the data. I would be interested to discuss these issues at the WebCamp event in Ireland but I am afraid I cannot be there in person. Hope to be able to follow the discussions here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pravin Tamkhane</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html/comment-page-1#comment-1353</link>
		<dc:creator>Pravin Tamkhane</dc:creator>
		<pubDate>Thu, 10 Jan 2008 08:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/01/privacy_and_rev.html#comment-1353</guid>
		<description>&quot;Innocent until proven guilty&quot; that says it all. Rather than trying to build a closed digital fortress, making revocation more strong will certainly make social networks more &quot;social&quot;. I mean, I really don&#039;t like concept of getting introduced to a unknown person on linkedin.com through the people I know. The whole reason I am there on linkedin.com is to get in touch with those whome I don&#039;t and NOT to whom I know already. And I think same applies for other social networks.
Great article!
Thanks, Pravin
</description>
		<content:encoded><![CDATA[<p>&#8220;Innocent until proven guilty&#8221; that says it all. Rather than trying to build a closed digital fortress, making revocation more strong will certainly make social networks more &#8220;social&#8221;. I mean, I really don&#8217;t like concept of getting introduced to a unknown person on linkedin.com through the people I know. The whole reason I am there on linkedin.com is to get in touch with those whome I don&#8217;t and NOT to whom I know already. And I think same applies for other social networks.<br />
Great article!<br />
Thanks, Pravin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Mullen</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/01/privacy_and_rev.html/comment-page-1#comment-1352</link>
		<dc:creator>Anthony Mullen</dc:creator>
		<pubDate>Mon, 07 Jan 2008 12:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/01/privacy_and_rev.html#comment-1352</guid>
		<description>Agree with the innocent until proven guilty approach. Rejection may even have a couple of reasons rather than the monolithic catchall of &#039;reject&#039;.
To ramp up the &#039;policing&#039; of those who spam or wildly friendadd the social network should keep tabs /stats on who is being rejected and why. That way pruning of the network (using collective intelligence about spammers) could happen either in an automated way or via admin intervention.
I would also be interested in further automated tools that &#039;find my time wasters&#039; which could be ran over my communications on the social network i.e. identify all those who post to me but I don&#039;t post to them OR identify senders that I only scan their message for &lt;2 seconds etc
I want my social networking &#039;automated butler&#039; to help me manage the front door.
p.s. your preview message function doesn&#039;t prompt for the catchpa &quot;who publishes open gardens&quot;
</description>
		<content:encoded><![CDATA[<p>Agree with the innocent until proven guilty approach. Rejection may even have a couple of reasons rather than the monolithic catchall of &#8216;reject&#8217;.<br />
To ramp up the &#8216;policing&#8217; of those who spam or wildly friendadd the social network should keep tabs /stats on who is being rejected and why. That way pruning of the network (using collective intelligence about spammers) could happen either in an automated way or via admin intervention.<br />
I would also be interested in further automated tools that &#8216;find my time wasters&#8217; which could be ran over my communications on the social network i.e. identify all those who post to me but I don&#8217;t post to them OR identify senders that I only scan their message for &lt;2 seconds etc<br />
I want my social networking &#8216;automated butler&#8217; to help me manage the front door.<br />
p.s. your preview message function doesn&#8217;t prompt for the catchpa &#8220;who publishes open gardens&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
