<?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: Facebook Changes Beacon to How it Should Have Been Designed in the First Place</title>
	<atom:link href="http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/</link>
	<description>information ethics : new media : privacy : values in design : 2.0</description>
	<lastBuildDate>Wed, 01 Sep 2010 17:47:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: michaelzimmer.org &#187; Michael Arrington is Wrong about Privacy, Too</title>
		<link>http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/comment-page-1/#comment-160456</link>
		<dc:creator>michaelzimmer.org &#187; Michael Arrington is Wrong about Privacy, Too</dc:creator>
		<pubDate>Wed, 13 Jan 2010 05:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/#comment-160456</guid>
		<description>[...] privacy-invading actions: changing the way information is shared among users of the system, or  creating a horribly-designed op-out interface that causes users&#8217; off-site actions to be posted in one&#8217;s news feed, or suddenly making [...]</description>
		<content:encoded><![CDATA[<p>[...] privacy-invading actions: changing the way information is shared among users of the system, or  creating a horribly-designed op-out interface that causes users&#8217; off-site actions to be posted in one&#8217;s news feed, or suddenly making [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaelzimmer.org &#187; Google Adds Location History to Latitude: Feature Request, or Strategic Rollout?</title>
		<link>http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/comment-page-1/#comment-160368</link>
		<dc:creator>michaelzimmer.org &#187; Google Adds Location History to Latitude: Feature Request, or Strategic Rollout?</dc:creator>
		<pubDate>Tue, 17 Nov 2009 04:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/#comment-160368</guid>
		<description>[...] these services from the start, just with a delay? Did Google learn the lessons of Facebook, who repeatedly bites off more than it can chew as it relates to users&#8217; privacy, and decided to launch [...]</description>
		<content:encoded><![CDATA[<p>[...] these services from the start, just with a delay? Did Google learn the lessons of Facebook, who repeatedly bites off more than it can chew as it relates to users&#8217; privacy, and decided to launch [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaelzimmer.org &#187; The Laws of Social Networking: Promote Open Flows of Information, Make Privacy Hard</title>
		<link>http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/comment-page-1/#comment-159908</link>
		<dc:creator>michaelzimmer.org &#187; The Laws of Social Networking: Promote Open Flows of Information, Make Privacy Hard</dc:creator>
		<pubDate>Sat, 13 Jun 2009 22:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/#comment-159908</guid>
		<description>[...] that share everything, and only make privacy changes when the pressure mounts (i.e., News Feed, Beacon, [...]</description>
		<content:encoded><![CDATA[<p>[...] that share everything, and only make privacy changes when the pressure mounts (i.e., News Feed, Beacon, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaelzimmer.org &#187; Privacy Trade-offs: Do People Not Care, or Simply Not Know?</title>
		<link>http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/comment-page-1/#comment-158339</link>
		<dc:creator>michaelzimmer.org &#187; Privacy Trade-offs: Do People Not Care, or Simply Not Know?</dc:creator>
		<pubDate>Sun, 01 Mar 2009 16:32:38 +0000</pubDate>
		<guid isPermaLink="false">http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/#comment-158339</guid>
		<description>[...] initial design of Beacon, where the defaults where to opt-into the information sharing [...]</description>
		<content:encoded><![CDATA[<p>[...] initial design of Beacon, where the defaults where to opt-into the information sharing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unit Structures &#8211; Facebook rethinks Beacon</title>
		<link>http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/comment-page-1/#comment-155403</link>
		<dc:creator>Unit Structures &#8211; Facebook rethinks Beacon</dc:creator>
		<pubDate>Fri, 22 Aug 2008 18:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://michaelzimmer.org/2007/11/29/facebook-changes-beacon-to-how-it-should-have-been-designed-in-the-first-place/#comment-155403</guid>
		<description>[...] reported in various blog and print sources, Facebook has announced changes to Beacon, the controversial ad program. According to the reports, [...]</description>
		<content:encoded><![CDATA[<p>[...] reported in various blog and print sources, Facebook has announced changes to Beacon, the controversial ad program. According to the reports, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
