<?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: relaunch: Google Reader</title>
	<atom:link href="http://nonsmokingarea.com/blog/2006/09/29/relaunch-google-reader/feed/" rel="self" type="application/rss+xml" />
	<link>http://nonsmokingarea.com/blog/2006/09/29/relaunch-google-reader/</link>
	<description>michael kamleitner - web-consultant &#38; -developer, vienna</description>
	<lastBuildDate>Sat, 17 Jul 2010 06:04:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nonsmokingarea.com &#187; Blog Archive &#187; blog-search to be added to google.com?</title>
		<link>http://nonsmokingarea.com/blog/2006/09/29/relaunch-google-reader/comment-page-1/#comment-3739</link>
		<dc:creator>nonsmokingarea.com &#187; Blog Archive &#187; blog-search to be added to google.com?</dc:creator>
		<pubDate>Thu, 23 Nov 2006 22:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://nonsmokingarea.com/blog/?p=378#comment-3739</guid>
		<description>[...] you might suppose Google should&#8217;nt really have a problem to establish their very own kick ass blog-index, but like their online RSS-reader, which has only gained attention after its recent major upgrade, blogsearch.google.com is living quite below the blogosphere&#8217;s radar. according to the screenshot (see below) blogger Andy Boyd has posted today, this might be subject to change in the very near future: in what might be a local beta-rollout, Andy seems to have received results from blogsearch mixed within the general results from google.com. [...]</description>
		<content:encoded><![CDATA[<p>[...] you might suppose Google should&#8217;nt really have a problem to establish their very own kick ass blog-index, but like their online RSS-reader, which has only gained attention after its recent major upgrade, blogsearch.google.com is living quite below the blogosphere&#8217;s radar. according to the screenshot (see below) blogger Andy Boyd has posted today, this might be subject to change in the very near future: in what might be a local beta-rollout, Andy seems to have received results from blogsearch mixed within the general results from google.com. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nonsmokingarea.com &#187; Blog Archive &#187; dev: Google Code Search</title>
		<link>http://nonsmokingarea.com/blog/2006/09/29/relaunch-google-reader/comment-page-1/#comment-1823</link>
		<dc:creator>nonsmokingarea.com &#187; Blog Archive &#187; dev: Google Code Search</dc:creator>
		<pubDate>Fri, 06 Oct 2006 00:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://nonsmokingarea.com/blog/?p=378#comment-1823</guid>
		<description>[...] looks like Google ain&#8217;t going to slow down these days: Code Search - Google&#8217;s effort on indexing source-code on the web - was launched earlier today. Code Search offers developers powerful ways (read: regular expressions) to search for code-snippets in any particular language, under any specific license. a quick test-drive unveiled that Code Search suffers from similar problems like established competitors Krugle and Koders: string-based search-results often mistake underlying semantics. when searching for an id3-implementation in PHP, results often lead to external function-calls, but not the actual source implementing id3. still, indexing source-code will definitely help making open source knowledge more accessible to average developers, not able/willing to spend hours/days to dissect code. looking forward on Danny Sullivan&#8217;s commentary on Code Search&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] looks like Google ain&#8217;t going to slow down these days: Code Search &#8211; Google&#8217;s effort on indexing source-code on the web &#8211; was launched earlier today. Code Search offers developers powerful ways (read: regular expressions) to search for code-snippets in any particular language, under any specific license. a quick test-drive unveiled that Code Search suffers from similar problems like established competitors Krugle and Koders: string-based search-results often mistake underlying semantics. when searching for an id3-implementation in PHP, results often lead to external function-calls, but not the actual source implementing id3. still, indexing source-code will definitely help making open source knowledge more accessible to average developers, not able/willing to spend hours/days to dissect code. looking forward on Danny Sullivan&#8217;s commentary on Code Search&#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
