<?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: Yahoo! Speeding Up Search</title>
	<atom:link href="http://staging.blog.biakelsey.com/index.php/2005/09/20/Yahoo-Speeding-Up-Search/feed/" rel="self" type="application/rss+xml" />
	<link>http://staging.blog.biakelsey.com/index.php/2005/09/20/Yahoo-Speeding-Up-Search/</link>
	<description>LOCAL MEDIA WATCH. The Nexus of All Things Local</description>
	<lastBuildDate>Mon, 01 Jun 2015 22:23:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.39</generator>
	<item>
		<title>By: Search Engines Web</title>
		<link>http://staging.blog.biakelsey.com/index.php/2005/09/20/Yahoo-Speeding-Up-Search/comment-page-1/#comment-422</link>
		<dc:creator><![CDATA[Search Engines Web]]></dc:creator>
		<pubDate>Tue, 20 Sep 2005 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-422</guid>
		<description><![CDATA[Wonder what the &quot;Sponsors&quot; think about this beta. :grrr: 

This is a convenient idea for the Surfers, but how far can this really go - it is a no-Profit feature (like the Google &quot;feel lucky&quot; button)

With PERSONALIZATION technology evolving, will that suggestion feature automatically &quot;infer&quot; what a user is likely to be looking for based on a profile.]]></description>
		<content:encoded><![CDATA[<p>Wonder what the &quot;Sponsors&quot; think about this beta. :grrr: </p>
<p>This is a convenient idea for the Surfers, but how far can this really go &#8211; it is a no-Profit feature (like the Google &quot;feel lucky&quot; button)</p>
<p>With PERSONALIZATION technology evolving, will that suggestion feature automatically &quot;infer&quot; what a user is likely to be looking for based on a profile.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
