<?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: How SHOULD dynamic privacy work?</title>
	<atom:link href="http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work</link>
	<description>Digital Lifestyle Aggregation - helping to establish open source infrastructure</description>
	<pubDate>Tue, 02 Dec 2008 12:49:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Internet Share information &#187; Blog Archive &#187; The battle for the future of the social web</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246347</link>
		<dc:creator>Internet Share information &#187; Blog Archive &#187; The battle for the future of the social web</dc:creator>
		<pubDate>Mon, 26 May 2008 05:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246347</guid>
		<description>[...] should contribute a specification for handling “dynamic privacy” that promotes the interests of its members (and which should work for individual web citizens at [...]</description>
		<content:encoded><![CDATA[<p>[...] should contribute a specification for handling “dynamic privacy” that promotes the interests of its members (and which should work for individual web citizens at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kazeloei</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246339</link>
		<dc:creator>Kazeloei</dc:creator>
		<pubDate>Sun, 25 May 2008 23:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246339</guid>
		<description>Hi webmaster!</description>
		<content:encoded><![CDATA[<p>Hi webmaster!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kazelfgh</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246338</link>
		<dc:creator>Kazelfgh</dc:creator>
		<pubDate>Sun, 25 May 2008 22:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246338</guid>
		<description>Hi webmaster!</description>
		<content:encoded><![CDATA[<p>Hi webmaster!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; What Facebook SHOULD do</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246205</link>
		<dc:creator>Marc&#8217;s Voice &#187; Blog Archive &#187; What Facebook SHOULD do</dc:creator>
		<pubDate>Tue, 20 May 2008 18:25:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246205</guid>
		<description>[...] Get dynamic privacy to work - correctly.  Nuf said.  Cause if you don&#8217;t, someone else - will.  You sure as hell BETTER start [...]</description>
		<content:encoded><![CDATA[<p>[...] Get dynamic privacy to work - correctly.  Nuf said.  Cause if you don&#8217;t, someone else - will.  You sure as hell BETTER start [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My data and having it my way &#171; Ungeek DaPo</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246176</link>
		<dc:creator>My data and having it my way &#171; Ungeek DaPo</dc:creator>
		<pubDate>Mon, 19 May 2008 19:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246176</guid>
		<description>[...] How SHOULD dynamic privacy work?, Marc Canter [...]</description>
		<content:encoded><![CDATA[<p>[...] How SHOULD dynamic privacy work?, Marc Canter [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: francine hardaway</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246153</link>
		<dc:creator>francine hardaway</dc:creator>
		<pubDate>Sun, 18 May 2008 23:51:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246153</guid>
		<description>I really think the most important piece of this conversation is the "relationship layer." Giving someone a business card, or an email address, is a minimal social contract. Friending them online is a little stronger contract. Then who owns the data? Probably the relationship. It's like marriage in a community property state: "with this business card/email address/profile access I thee wed." And you bet that's dynamic! And very complex</description>
		<content:encoded><![CDATA[<p>I really think the most important piece of this conversation is the &#8220;relationship layer.&#8221; Giving someone a business card, or an email address, is a minimal social contract. Friending them online is a little stronger contract. Then who owns the data? Probably the relationship. It&#8217;s like marriage in a community property state: &#8220;with this business card/email address/profile access I thee wed.&#8221; And you bet that&#8217;s dynamic! And very complex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; The people united will never be defeated</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246130</link>
		<dc:creator>Marc&#8217;s Voice &#187; Blog Archive &#187; The people united will never be defeated</dc:creator>
		<pubDate>Sun, 18 May 2008 06:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246130</guid>
		<description>[...] What we need is dynamic privacy - working correctly.  [...]</description>
		<content:encoded><![CDATA[<p>[...] What we need is dynamic privacy - working correctly.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elias Bizannes</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246127</link>
		<dc:creator>Elias Bizannes</dc:creator>
		<pubDate>Sun, 18 May 2008 04:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246127</guid>
		<description>Good post!

Loving how you are helping drive the conversation - keep it up.</description>
		<content:encoded><![CDATA[<p>Good post!</p>
<p>Loving how you are helping drive the conversation - keep it up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dynamic Privacy, protection of &#8216;my data&#8217;, Friend Connect &#124; what is all the fuss about? &#171; The Bankwatch</title>
		<link>http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246120</link>
		<dc:creator>Dynamic Privacy, protection of &#8216;my data&#8217;, Friend Connect &#124; what is all the fuss about? &#171; The Bankwatch</dc:creator>
		<pubDate>Sat, 17 May 2008 22:28:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.broadbandmechanics.com/2008/05/how-should-dynamic-privacy-work#comment-246120</guid>
		<description>[...] Marc’s Voice » Blog Archive » How SHOULD dynamic privacy work? By that I mean - clearly Facebook wants to keep their user’s data in their system, but they have to answer all our demands for allowing user’s to move their data or at least access their data - from remote locations. [...]</description>
		<content:encoded><![CDATA[<p>[...] Marc’s Voice » Blog Archive » How SHOULD dynamic privacy work? By that I mean - clearly Facebook wants to keep their user’s data in their system, but they have to answer all our demands for allowing user’s to move their data or at least access their data - from remote locations. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
