<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Soapbox Ramblings &#187; f8</title>
	<atom:link href="http://blog.yellowrosedesigns.net/tag/f8/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.yellowrosedesigns.net</link>
	<description>Design Blog</description>
	<lastBuildDate>Mon, 11 Apr 2011 14:24:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Facebook Faux Pas</title>
		<link>http://yellowrosewebdesign.com/2010/04/facebook-faux-pas/</link>
		<comments>http://yellowrosewebdesign.com/2010/04/facebook-faux-pas/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 18:15:28 +0000</pubDate>
		<dc:creator>Kat</dc:creator>
				<category><![CDATA[General Rants]]></category>
		<category><![CDATA[cloak and dagger]]></category>
		<category><![CDATA[developer's conference]]></category>
		<category><![CDATA[f8]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[facebook policies]]></category>
		<category><![CDATA[facebook privacy]]></category>
		<category><![CDATA[fans]]></category>
		<category><![CDATA[like button]]></category>
		<category><![CDATA[privacy]]></category>

		<guid isPermaLink="false">http://blog.yellowrosedesigns.net/?p=135</guid>
		<description><![CDATA[It&#8217;s been a week since Facebook made changes to their site that affected anyone with a &#8220;Fan Page.&#8221; We no longer have Fans, we have people who &#8220;Like&#8221; our pages. Users and page owners began noticing the change on April 20, the day before F8, the Facebook Developer&#8217;s Conference. Before the conference even began, and [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><img class="wp-smiley" src="http://yellowrosedesigns.net/blog/images/f-bk-thumbdown.png" alt="Like?" hspace="3" vspace="3" align="left" />It&#8217;s been a week since Facebook made  changes to their site that  affected anyone with a &#8220;Fan  Page.&#8221; We no longer have Fans, we have people who &#8220;Like&#8221; our  pages. Users and page owners began noticing the change on April 20,  the day before F8, the Facebook Developer&#8217;s Conference. Before the  conference even began, and long before the keynote speech by Mark  Zuckerberg and Bret Taylor, thousands of upset page owners began  putting up pages and groups asking to bring the &#8220;Fans&#8221; back. One  group alone had 3,000 new members within an hour. I not only  understand their frustration, I felt it too. If we only have people  who &#8220;like&#8221; our pages now, how are we supposed to recruit new  Fans? Do we say, &#8220;Please like me!&#8221; and sound like we&#8217;re begging?  Or, &#8220;Become a Liker&#8221;, which sounds . . . well, that just sounds a  bit dirty. &#8220;Become a Fan&#8221; was easier to understand. Now page  owners are scrambling to change websites, advertising campaigns and  any outside references to Facebook. Not to mention, that <em>now</em> when someone &#8220;likes&#8221; a Facebook page, 1. their friends can no  longer comment on it; and 2. if a friend &#8220;likes&#8221; that they liked  it, that friend is suddenly a fan of the page too. Which, ok, is  fine, <em>in theory</em>. Facebook figures if I &#8220;like&#8221; that they liked it, I would want to be a fan too. But I  would rather not become a fan of pages like &#8220;Real women ain&#8217;t a  size 0 &#8230; Real women have curves&#8221;, even though I might &#8220;like&#8221;  that my male friends are fans of that page. <img src='http://blog.yellowrosedesigns.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>I  discovered F8 in my search to find out what had happened to our  pages. If you want to see the keynote speech for yourself, as of now,  it&#8217;s still available here: <a href="http://apps.facebook.com/feightlive/" target="_blank">http://apps.facebook.com/feightlive/</a>. The  keynote itself is geared for developers, so be warned. Some  interesting facts for Facebook users that have been misreported and  misunderstood all over the web (and sparked some heated comments over  at <a href="http://mashable.com/2010/04/21/open-graph-privacy/" target="_blank">Mashable</a>) &#8211; the changes to their policies.</p>
<ol>
<li>One  	step permission &#8211; From now on when someone wants to allow an  	application (that would be all those games that you play, quizzes,  	gift apps, etc) or a website that might use this in the future, you  	click &#8220;Allow&#8221; only once for the application developer to access  	your Facebook information. If you think about it, when you enjoy or  	trust a game or app, don&#8217;t you generally &#8220;Allow&#8221; it to access  	your Facebook information already? (If you&#8217;re not sure, you can  	check your account&#8217;s application settings. You might be surprised  	how many apps you&#8217;ve allowed access to your profile.)</li>
<li>Removing  	the policy for developers, &#8220;You must not store or cache any data  	you receive from us for more than 24 hours. . .&#8221; What does this  	mean to users? <em>Absolutely nothing.</em> As a user, once you gave an app access to your information, they  	were allowed by Facebook to go and retrieve that information anytime  	they wanted. They just couldn&#8217;t keep it. The change is on the developer&#8217;s side only. Now they  	don&#8217;t have to ask Facebook&#8217;s permission to access your profile every  	time you play their game (Admit it! You know that&#8217;s almost every  	day!) And it is up to the developer to remove your information if  	you ever stop allowing them access. As a side-note, what I learned  	while chatting to developers during the keynote is that nearly every  	developer out there got around that policy anyway. If you ever  	allowed any unscrupulous developer access to your information even  	once, you may as well have given him access for life. Most of  	the developers out there are using your permissions only for what it  	was intended &#8211; for you to have access to their fun games and  	widgets.</li>
<li> The  	third important item relates less to policy change and more to  	Facebook implementing a new feature for other sites outside of  	Facebook. We can now add the Facebook &#8220;Like&#8221; button to our  	sites, along with comments and other nifty little Social Plugin  	features. Does this mean I automatically have access to your  	Facebook information? No. I have no more access to your  	personal information on my site than I do if you become a Fan of my  	page. The only way sites have access to personal information is just  	like Facebook already uses: The user must <em>allow</em> the site access, through a secure Facebook-hosted application.</li>
</ol>
<blockquote><p>Quote  directly from <a href="http://www.facebook.com/sitetour/connect.php" target="_blank">Facebook</a>:  &#8220;None of your data is shared with the site when you view social  plugins. Social plugins pull information directly from Facebook and  the site has no access to the data being displayed to you.&#8221;</p></blockquote>
<p>Zuckerberg is clearly pushing the new  &#8220;Like&#8221; button that Facebook has made available to other websites.  If you want to see this in action, I&#8217;ve added a &#8220;Like&#8221; button to  this blog and a &#8220;Like/Comment&#8221; button to my <a href="http://www.yellowrosedesigns.net/supernatural-deans-amulet/">Supernatural page for  Dean&#8217;s Amulet</a>. So, yes, I can start to see where they were going with  the new &#8220;Like&#8221; feature. Zuckerberg wants you to &#8220;Like&#8221; a  particular restaurant or band. I want you to Like my blog and the  products I sell on my site. <img src='http://blog.yellowrosedesigns.net/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>I saw some page owners calling the  change a &#8220;database grab&#8221;. Uh, hello? It&#8217;s <em>their</em> database. We&#8217;re just along for the ride. What Facebook did <em>not</em> consider were the implications the change would have to other people.  Facebook now has 400 million users. Three-thousand of them jumping up  and down <img class="wp-smiley" src="http://www.rocksaltjournals.com/forum/mods/smileys/images/ranting.gif" alt="ranting" /> about the &#8220;Fan&#8221; button probably aren&#8217;t going to make a  very big wave. And that&#8217;s the biggest faux pas they could make.  Facebook seems to care only about <em>Facebook</em>.  Rolling out a significant change to the functionality of their site  literally overnight, and with no mention of it other than in a  conference for developers &#8211; in other words, <em>obscure</em> to most of their actual 400 million users &#8211; comes across as a cloak  and dagger scheme. And this from a company who claims to be open  about their policies. Open source for developers, maybe, but as secretive as Google when it comes to their users. Why is Facebook not out there announcing to its users what  they&#8217;re doing and why? Why aren&#8217;t they telling them &#8220;No, we&#8217;re not  going to start charging to use our site.&#8221;? (They aren&#8217;t.) Why aren&#8217;t they letting Page owners know in advance that something important is about to change on Facebook Pages? If I had  seen the announcement about the &#8220;Like&#8221; button before suddenly  discovering it on my page without warning, the transition would have  gone much more smoothly. Facebook can&#8217;t seem to see the forest for  all the 400 million trees. Their developers are busily rolling out  changes (That weren&#8217;t ready to be rolled out. There were some serious  errors on the Open Graph/Social Plugins documentation that weren&#8217;t  corrected until almost 2 days after the conference, again, in cloak  and dagger style.) without giving thought to all the possible  scenarios or impact on the one thing that makes Facebook what it is &#8211; <em>each</em> of the 400  million users. Here&#8217;s hoping that by the time their next developer&#8217;s  conference comes around, they&#8217;ve learned a very important lesson &#8211; <em>People</em> are what make  &#8220;social interactions&#8221; happen. Not programs.</p>
<p>Oh,  and as for the question of how do I recruit new users to my Facebook  Page? I simply ask you to <a href="http://www.facebook.com/YellowRoseDesigns" target="_blank">Connect with Me</a>. <img src='http://blog.yellowrosedesigns.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p class="copy"><em>&#8220;Facebook is a registered trademark of Facebook, Inc.&#8221;</em></p>
]]></content:encoded>
			<wfw:commentRss>http://yellowrosewebdesign.com/2010/04/facebook-faux-pas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
