<?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>Ben Foster &#187; search</title>
	<atom:link href="http://www.benphoster.com/tag/search/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.benphoster.com</link>
	<description>Ben Foster on Digital Strategy, Social Media, and the Corner Office</description>
	<lastBuildDate>Wed, 14 Dec 2011 00:05:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Facebook&#8217;s Strategy is Forcing Us to Categorize our Friends by Delaying Real-Time Search</title>
		<link>http://www.benphoster.com/facebooks-strategy-is-forcing-us-to-categorize-our-friends-by-delaying-real-time-search/</link>
		<comments>http://www.benphoster.com/facebooks-strategy-is-forcing-us-to-categorize-our-friends-by-delaying-real-time-search/#comments</comments>
		<pubDate>Mon, 16 Mar 2009 16:23:24 +0000</pubDate>
		<dc:creator>Ben Foster</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Strategy]]></category>
		<category><![CDATA[friends]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.benphoster.com/?p=347</guid>
		<description><![CDATA[Now that all your friends have stopped wondering whether or not they like the New Facebook Changes, we can study what this is doing for Facebook and it&#8217;s users.  First, here&#8217;s Jared W. Smith with a great summary of the changes: The area where you enter status updates has been made into a more ambiguous [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 30px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.benphoster.com%2Ffacebooks-strategy-is-forcing-us-to-categorize-our-friends-by-delaying-real-time-search%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.benphoster.com%2Ffacebooks-strategy-is-forcing-us-to-categorize-our-friends-by-delaying-real-time-search%2F&amp;source=benphoster&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://www.benphoster.com/wp-content/uploads/2009/03/friend.jpg"><img class="size-medium wp-image-350 alignright" style="border: 10px solid black;" title="friend" src="http://www.benphoster.com/wp-content/uploads/2009/03/friend-133x300.jpg" alt="friend" width="130" height="300" /></a>Now that all your friends have stopped wondering whether or not they like the <a href="http://laurelpapworth.com/new-facebook-features-filter-stream-publisher/">New Facebook Changes</a>, we can study what this is doing for Facebook and it&#8217;s users.  First, here&#8217;s Jared W. Smith with <a href="http://jaredwsmith.com/2009/03/14/new-facebook-consistently-inconsistent/" target="_blank">a great summary of the changes</a>:</p>
<blockquote><p>The area where you enter status updates has been made into a more ambiguous “publisher” which will post status updates, notes, photos, and the like. &#8230;  A lot’s been made of a comparison to Twitter, but I think FriendFeed is a far more effective analogy because of the range of items you can share &#8230; Facebook was pretty straightforward to use because a status update was a status update, a photo post was a photo post, and the like. It’s all been melded together now&#8230;</p></blockquote>
<p><strong>Where&#8217;s the Real-Time Search?</strong></p>
<p>With all the recent talk about <a href="http://www.eweek.com/c/a/Enterprise-Applications/Twitter-Search-Feature-a-Threat-to-Google/" target="_blank">Twitter threatening Google </a>(unlikely, Google has massive amounts of personal data) why didn&#8217;t Facebook include a Real-Time Search like Twitter?  For example, this weekend I wanted see which friends were at the <a href="http://en.wikipedia.org/wiki/South_by_Southwestl">South by Southwest conference (SXSW)</a> but couldn&#8217;t.  So I went through hundreds of updates trying to find out.</p>
<p><strong>Facebook is Forcing  Friend Categorization</strong></p>
<p>The seemingly intentional omission of real-time search suggests that Facebook&#8217;s strategy is to solve for real-time search by forcing Friend Categorization.   I found myself wanting to organize friends into a &#8220;tech&#8221; friend group because those would be the most likely attendees of <a href="http://en.wikipedia.org/wiki/South_by_Southwestl" target="_blank">SXSW</a>.</p>
<p><strong>Friend Tagging/Categorizing is Insanely Valuable to Facebook</strong></p>
<p>Facebook benefits if users are labeling, tagging, and categorizing their network.  Most of us aren&#8217;t self-aware enough to properly label ourselves, so having our network label us (anonymously) provides a hyper-accurate categorization of who we are.</p>
<p><strong>Search is probably coming&#8230;but not until we&#8217;re all labeled</strong></p>
<p>It&#8217;s easy for Facebook to implement real-time search and it is <a href="http://www.webpronews.com/topnews/2009/02/23/twitter-homepage-search-could-test-google" target="_blank">valuable to users</a>.  Facebook is intentionally waiting to roll it out until we&#8217;ve all done our job helping Facebook categorize ourselves.   As a user&#8230;I don&#8217;t know if I&#8217;ll ever spend the time to organize everyone.  As a strategist, I congratulate you Facebook.  Great move.</p>
<p><strong><br />
</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.benphoster.com/facebooks-strategy-is-forcing-us-to-categorize-our-friends-by-delaying-real-time-search/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

