<?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: Sources for Social Networking Privacy</title>
	<atom:link href="http://infoadvocate.org/blog/2008/04/24/sources-for-social-networking-privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://infoadvocate.org/blog/2008/04/24/sources-for-social-networking-privacy/</link>
	<description>Information Privacy Advocacy</description>
	<pubDate>Sat, 30 Aug 2008 11:20:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: InfoAdvocate &#187; As the Web Goes Social, Where Is Privacy?</title>
		<link>http://infoadvocate.org/blog/2008/04/24/sources-for-social-networking-privacy/#comment-952</link>
		<dc:creator>InfoAdvocate &#187; As the Web Goes Social, Where Is Privacy?</dc:creator>
		<pubDate>Tue, 20 May 2008 20:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://infoadvocate.org/blog/?p=33#comment-952</guid>
		<description>[...] privacy. Timothy Lee at Techdirt blogged on how data portability could mitigate privacy issues. I previously blogged about a position paper from ENISA on social networking security recommendations. They noted (pdf): [...]</description>
		<content:encoded><![CDATA[<p>[...] privacy. Timothy Lee at Techdirt blogged on how data portability could mitigate privacy issues. I previously blogged about a position paper from ENISA on social networking security recommendations. They noted (pdf): [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
