<?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: VibeAgent and the future of social search</title>
	<atom:link href="http://www.timpeter.com/blog/2007/11/15/vibeagent-and-the-future-of-social-search/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.timpeter.com/blog/2007/11/15/vibeagent-and-the-future-of-social-search/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=vibeagent-and-the-future-of-social-search</link>
	<description>Interactive marketing and e-commerce strategy blog for the local, mobile, social web</description>
	<lastBuildDate>Wed, 08 Feb 2012 18:08:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The joys of social search. And regular old search, too (Small Business E-commerce Link Digest &#8211; October 23, 2009)</title>
		<link>http://www.timpeter.com/blog/2007/11/15/vibeagent-and-the-future-of-social-search/comment-page-1/#comment-3715</link>
		<dc:creator>The joys of social search. And regular old search, too (Small Business E-commerce Link Digest &#8211; October 23, 2009)</dc:creator>
		<pubDate>Fri, 23 Oct 2009 21:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.timpeter.com/blog/2007/11/15/vibeagent-and-the-future-of-social-search/#comment-3715</guid>
		<description>[...] search, with both Microsoft and Google signing deals with Twitter. We&#8217;ve been wondering when social search was going to happen for a while now. Nice to see the big boys get in the [...]</description>
		<content:encoded><![CDATA[<p>[...] search, with both Microsoft and Google signing deals with Twitter. We&#8217;ve been wondering when social search was going to happen for a while now. Nice to see the big boys get in the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

