<?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: Glue, Web 2.0 and the Next Google</title> <atom:link href="http://twopointouch.com/2008/business/glue-web-20-and-the-next-google/feed/" rel="self" type="application/rss+xml" /><link>http://twopointouch.com/2008/business/glue-web-20-and-the-next-google/</link> <description>web 2.0, blogs and social media</description> <lastBuildDate>Mon, 30 May 2011 20:58:01 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1.3</generator> <item><title>By: Connecting News, Commentaries and Blogs at NineReports.com -</title><link>http://twopointouch.com/2008/business/glue-web-20-and-the-next-google/#comment-12238</link> <dc:creator>Connecting News, Commentaries and Blogs at NineReports.com -</dc:creator> <pubDate>Sat, 02 Feb 2008 00:56:22 +0000</pubDate> <guid
isPermaLink="false">http://twopointouch.com/2008/01/04/glue-web-20-and-the-next-google/#comment-12238</guid> <description>[...] a ...  cardgames collection cards - Last Updated -  55 minutes ago&#160;    Request a Trackback     Glue, Web 2.0 and the Next Google  If you were a brand manager for an FMCG company - let&#8217;s say you look after Bostik, for the [...]</description> <content:encoded><![CDATA[<p>[…] a …  cardgames collection cards — Last Updated —  55 minutes ago     Request a Trackback     Glue, Web 2.0 and the Next Google  If you were a brand manager for an FMCG company — let’s say you look after Bostik, for the […]</p> ]]></content:encoded> </item> <item><title>By: ??? &#62; OLDaily ??? &#187; Blog Archive &#187; 2008?1?4? ???? IMS?? ???? Intel??OLPC ?????</title><link>http://twopointouch.com/2008/business/glue-web-20-and-the-next-google/#comment-12131</link> <dc:creator>??? &#62; OLDaily ??? &#187; Blog Archive &#187; 2008?1?4? ???? IMS?? ???? Intel??OLPC ?????</dc:creator> <pubDate>Mon, 07 Jan 2008 15:47:39 +0000</pubDate> <guid
isPermaLink="false">http://twopointouch.com/2008/01/04/glue-web-20-and-the-next-google/#comment-12131</guid> <description>[...] Delaney, twopointouch January 4, 2008 [????] [Tags: Networks, Web 2.0, Google] [...]</description> <content:encoded><![CDATA[<p>[…] Delaney, twopointouch January 4, 2008 [????] [Tags: Networks, Web 2.0, Google] […]</p> ]]></content:encoded> </item> <item><title>By: Damon</title><link>http://twopointouch.com/2008/business/glue-web-20-and-the-next-google/#comment-12127</link> <dc:creator>Damon</dc:creator> <pubDate>Mon, 07 Jan 2008 02:53:16 +0000</pubDate> <guid
isPermaLink="false">http://twopointouch.com/2008/01/04/glue-web-20-and-the-next-google/#comment-12127</guid> <description>Maybe there won&#039;t be a next Google.
I think Google is great for finding new, rapidly changing information, but it is pretty weak when you are looking for authorative information that doesn&#039;t change every couple of weeks.
Searching Google for PHP error codes, for example, frequently turns up recent forum posts by people who didn&#039;t bother searching for the answer first. A few comprehensive pages explaining the error codes would be much more useful than &quot;I&#039;m getting this error; please fix it&quot; posts.
History is another example of a subject where fresh content mostly shouldn&#039;t be found at the top of the search results.
The point is that, instead of trying to recognise the value of new content faster than Google, there is space for a search engine to specialise in content that doesn&#039;t need to be fresh.</description> <content:encoded><![CDATA[<p>Maybe there won’t be a next Google.</p><p>I think Google is great for finding new, rapidly changing information, but it is pretty weak when you are looking for authorative information that doesn’t change every couple of weeks.</p><p>Searching Google for PHP error codes, for example, frequently turns up recent forum posts by people who didn’t bother searching for the answer first. A few comprehensive pages explaining the error codes would be much more useful than “I’m getting this error; please fix it” posts.</p><p>History is another example of a subject where fresh content mostly shouldn’t be found at the top of the search results.</p><p>The point is that, instead of trying to recognise the value of new content faster than Google, there is space for a search engine to specialise in content that doesn’t need to be fresh.</p> ]]></content:encoded> </item> </channel> </rss>
