<?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: Thoughts on dynamic privacy</title>
	<atom:link href="http://factoryjoe.com/blog/2008/06/11/thoughts-on-dynamic-privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2008/06/11/thoughts-on-dynamic-privacy/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<pubDate>Fri, 21 Nov 2008 14:07:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: The Song Remains The Same &#187; Blog Archive &#187; The Coming Economics of Big Data</title>
		<link>http://factoryjoe.com/blog/2008/06/11/thoughts-on-dynamic-privacy/#comment-99435</link>
		<dc:creator>The Song Remains The Same &#187; Blog Archive &#187; The Coming Economics of Big Data</dc:creator>
		<pubDate>Tue, 24 Jun 2008 03:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=958#comment-99435</guid>
		<description>[...] Data generally wants users to be able to have access to their data via third parties, but only in very limited conditions. I would classify these limitations as &#8220;artificial constraints&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Data generally wants users to be able to have access to their data via third parties, but only in very limited conditions. I would classify these limitations as &#8220;artificial constraints&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Siddey</title>
		<link>http://factoryjoe.com/blog/2008/06/11/thoughts-on-dynamic-privacy/#comment-99399</link>
		<dc:creator>Siddey</dc:creator>
		<pubDate>Wed, 18 Jun 2008 13:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=958#comment-99399</guid>
		<description>Chris,

A great interview and yet again you've provided some great insights into the secret sauce behind the next generation of online social and location enabled services. It's all about context and relevance.

I've also thrown my hat in the ring and attempted to break-down the elements that will define relevance for mobile location services. Let me know what you think.

http://siddey.wordpress.com/2008/06/18/defining-information-relevance-for-location-based-services/</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>A great interview and yet again you&#8217;ve provided some great insights into the secret sauce behind the next generation of online social and location enabled services. It&#8217;s all about context and relevance.</p>
<p>I&#8217;ve also thrown my hat in the ring and attempted to break-down the elements that will define relevance for mobile location services. Let me know what you think.</p>
<p><a href="http://siddey.wordpress.com/2008/06/18/defining-information-relevance-for-location-based-services/" rel="nofollow">http://siddey.wordpress.com/2008/06/18/defining-information-relevance-for-location-based-services/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sumeet Singh</title>
		<link>http://factoryjoe.com/blog/2008/06/11/thoughts-on-dynamic-privacy/#comment-99369</link>
		<dc:creator>Sumeet Singh</dc:creator>
		<pubDate>Fri, 13 Jun 2008 10:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=958#comment-99369</guid>
		<description>Nice article. Although Facebook has been on a privacy watchlist for a long time, measures such as these are bound to contribute to a safe internet.</description>
		<content:encoded><![CDATA[<p>Nice article. Although Facebook has been on a privacy watchlist for a long time, measures such as these are bound to contribute to a safe internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave mcclure</title>
		<link>http://factoryjoe.com/blog/2008/06/11/thoughts-on-dynamic-privacy/#comment-99346</link>
		<dc:creator>dave mcclure</dc:creator>
		<pubDate>Wed, 11 Jun 2008 20:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=958#comment-99346</guid>
		<description>my thoughts on how to make this work, from a few weeks ago:

http://500hats.typepad.com/500blogs/2008/05/memo-to-google.html

"Memo to Google, Yahoo, Microsoft, &#38; AOL: How to Turn 500M email logins into Facebook Platform &#38; a Crapload of Revenue"

basically, by constraining the # of friend list connections to the top most relevant (as determined by messaging frequency + keyword relevance), you can actually IMPROVE usability &#38; adoption by CONSTRAINING the # of choices / friends.

i don't have a strong opinion on the tools / standards / methods to get there, but the user experience should be relatively similar -- WITHOUT having to give away an email address.</description>
		<content:encoded><![CDATA[<p>my thoughts on how to make this work, from a few weeks ago:</p>
<p><a href="http://500hats.typepad.com/500blogs/2008/05/memo-to-google.html" rel="nofollow">http://500hats.typepad.com/500blogs/2008/05/memo-to-google.html</a></p>
<p>&#8220;Memo to Google, Yahoo, Microsoft, &amp; AOL: How to Turn 500M email logins into Facebook Platform &amp; a Crapload of Revenue&#8221;</p>
<p>basically, by constraining the # of friend list connections to the top most relevant (as determined by messaging frequency + keyword relevance), you can actually IMPROVE usability &amp; adoption by CONSTRAINING the # of choices / friends.</p>
<p>i don&#8217;t have a strong opinion on the tools / standards / methods to get there, but the user experience should be relatively similar &#8212; WITHOUT having to give away an email address.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
