<?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: Facebook Hate</title>
	<atom:link href="http://www.marclehmann.net/2007/11/facebook-hate/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marclehmann.net/2007/11/facebook-hate/</link>
	<description>are you playing the game or watching from the stands?</description>
	<pubDate>Tue, 02 Dec 2008 01:18:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: grant</title>
		<link>http://www.marclehmann.net/2007/11/facebook-hate/#comment-13</link>
		<dc:creator>grant</dc:creator>
		<pubDate>Wed, 05 Dec 2007 10:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.marclehmann.net/2007/11/facebook-hate/#comment-13</guid>
		<description>The inevitable &lt;a href="http://news.bbc.co.uk/2/hi/technology/7120916.stm" rel="nofollow"&gt;about face&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>The inevitable <a href="http://news.bbc.co.uk/2/hi/technology/7120916.stm" rel="nofollow">about face</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc</title>
		<link>http://www.marclehmann.net/2007/11/facebook-hate/#comment-12</link>
		<dc:creator>marc</dc:creator>
		<pubDate>Tue, 04 Dec 2007 16:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.marclehmann.net/2007/11/facebook-hate/#comment-12</guid>
		<description>thanks, i do that quite regularly. it's like sweeping the front porch :)</description>
		<content:encoded><![CDATA[<p>thanks, i do that quite regularly. it&#8217;s like sweeping the front porch <img src='http://www.marclehmann.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grant</title>
		<link>http://www.marclehmann.net/2007/11/facebook-hate/#comment-11</link>
		<dc:creator>grant</dc:creator>
		<pubDate>Tue, 04 Dec 2007 10:21:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.marclehmann.net/2007/11/facebook-hate/#comment-11</guid>
		<description>The plot thickens: &lt;a href="http://labs.echoditto.com/facebook-beacon" rel="nofollow"&gt;Facebook still provides your details after you've logged out&lt;/a&gt;. So if you leave Facebook, make sure you kill your cookies too...</description>
		<content:encoded><![CDATA[<p>The plot thickens: <a href="http://labs.echoditto.com/facebook-beacon" rel="nofollow">Facebook still provides your details after you&#8217;ve logged out</a>. So if you leave Facebook, make sure you kill your cookies too&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grant</title>
		<link>http://www.marclehmann.net/2007/11/facebook-hate/#comment-10</link>
		<dc:creator>grant</dc:creator>
		<pubDate>Thu, 29 Nov 2007 18:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.marclehmann.net/2007/11/facebook-hate/#comment-10</guid>
		<description>The core issue at play, as I see it, is that Facebook could have easily made this an "opt-in" feature, and they didn't. With their existing features their invite/opt-in based. This isn't.

And it's that implied "promise" that is at stake here. Facebook has terms and conditions, but the implied promise to date is "we'll let you opt-in". There are subtle differences in approach with Beacon that break this.

And, although I honestly haven't seen the commentary you refer to in terms of user's rights, I think this is the core of the argument. When creating a big community site like this, there is a power-play at work. And when enough users revolt, it can have pretty intense results - witness the recent overtaking of Digg by it's members over censorship.

Although legally Facebook's T&#038;Cs are sound and give them the permission they need to do what they're doing, that's not the dynamic or expectation of their community. And with that trust broken, Facebook has a real dilemma.

If they don't re-structure Beacon to be truly opt-in, they risk a serious backlash that could really stunt their growth (I'm not suggesting they will collapse or anything as dramatic as that, just that the space becomes much less appealing to new and existing users, and they start looking elsewhere).

Yet if they change their approach, they risk alienating their advertisers at worst, or at best, reducing the value proposition of what is (honestly) a really interesting and innovative approach to marketing/advertising in the social media space. Which, of course, damages their ability to monetize the massive community they've built.

I've just finished reading an article in Fast Company, and the founders are innately aware that their user base is the only true asset they've got - so I think they'll ultimately change their current practice to be more truly opt-in, or at least tweak the feature to resolve some of the more serious issues.

But it will be interesting to see how they approach it and how it resolves...</description>
		<content:encoded><![CDATA[<p>The core issue at play, as I see it, is that Facebook could have easily made this an &#8220;opt-in&#8221; feature, and they didn&#8217;t. With their existing features their invite/opt-in based. This isn&#8217;t.</p>
<p>And it&#8217;s that implied &#8220;promise&#8221; that is at stake here. Facebook has terms and conditions, but the implied promise to date is &#8220;we&#8217;ll let you opt-in&#8221;. There are subtle differences in approach with Beacon that break this.</p>
<p>And, although I honestly haven&#8217;t seen the commentary you refer to in terms of user&#8217;s rights, I think this is the core of the argument. When creating a big community site like this, there is a power-play at work. And when enough users revolt, it can have pretty intense results - witness the recent overtaking of Digg by it&#8217;s members over censorship.</p>
<p>Although legally Facebook&#8217;s T&#038;Cs are sound and give them the permission they need to do what they&#8217;re doing, that&#8217;s not the dynamic or expectation of their community. And with that trust broken, Facebook has a real dilemma.</p>
<p>If they don&#8217;t re-structure Beacon to be truly opt-in, they risk a serious backlash that could really stunt their growth (I&#8217;m not suggesting they will collapse or anything as dramatic as that, just that the space becomes much less appealing to new and existing users, and they start looking elsewhere).</p>
<p>Yet if they change their approach, they risk alienating their advertisers at worst, or at best, reducing the value proposition of what is (honestly) a really interesting and innovative approach to marketing/advertising in the social media space. Which, of course, damages their ability to monetize the massive community they&#8217;ve built.</p>
<p>I&#8217;ve just finished reading an article in Fast Company, and the founders are innately aware that their user base is the only true asset they&#8217;ve got - so I think they&#8217;ll ultimately change their current practice to be more truly opt-in, or at least tweak the feature to resolve some of the more serious issues.</p>
<p>But it will be interesting to see how they approach it and how it resolves&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
