<?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: links for 2007-08-16</title>
	<atom:link href="http://www.nxtbookmedia.com/blog/2007/08/16/links-for-2007-08-16/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nxtbookmedia.com/blog/2007/08/16/links-for-2007-08-16/</link>
	<description>The blog of Nxtbook Media</description>
	<lastBuildDate>Thu, 22 Dec 2011 23:08:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Matthew</title>
		<link>http://www.nxtbookmedia.com/blog/2007/08/16/links-for-2007-08-16/comment-page-1/#comment-42078</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Thu, 13 Sep 2007 18:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbook.com/blog/2007/08/16/links-for-2007-08-16/#comment-42078</guid>
		<description>This is a good question and the answer reflects on Google&#039;s (sometimes questioned) philosophy of &quot;Do No Evil&quot;. In reality, Google only bans cloaking when it is used for inappropriate purposes, such as trying to artificially inflate search rankings.  As far back as 2003, Danny Sullivan wrote that XML feeds are a form of approved cloaking (link: http://www.clickz.com/2107941/print ). Most rich internet applications, such as the Nxtbook, need to present a different view of the content to Google&#039;s indexing bots since Google is currently unable to index rich content developed with technologies such as Flash, Ajax, Silverlight, etc.  As you can see by clicking on the above Google search, Google does not have any problem indexing our content, even though we are using our Hybrid Flash technology. In the past several months, we&#039;ve seen a dramatic increase in the amount of activity to Nxtbooks via Google. We consider this proof that Google is confident that what we&#039;re doing is wholly appropriate.</description>
		<content:encoded><![CDATA[<p>This is a good question and the answer reflects on Google&#8217;s (sometimes questioned) philosophy of &#8220;Do No Evil&#8221;. In reality, Google only bans cloaking when it is used for inappropriate purposes, such as trying to artificially inflate search rankings.  As far back as 2003, Danny Sullivan wrote that XML feeds are a form of approved cloaking (link: <a href="http://www.clickz.com/2107941/print" rel="nofollow">http://www.clickz.com/2107941/print</a> ). Most rich internet applications, such as the Nxtbook, need to present a different view of the content to Google&#8217;s indexing bots since Google is currently unable to index rich content developed with technologies such as Flash, Ajax, Silverlight, etc.  As you can see by clicking on the above Google search, Google does not have any problem indexing our content, even though we are using our Hybrid Flash technology. In the past several months, we&#8217;ve seen a dramatic increase in the amount of activity to Nxtbooks via Google. We consider this proof that Google is confident that what we&#8217;re doing is wholly appropriate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stevie D Marsh</title>
		<link>http://www.nxtbookmedia.com/blog/2007/08/16/links-for-2007-08-16/comment-page-1/#comment-39585</link>
		<dc:creator>Stevie D Marsh</dc:creator>
		<pubDate>Mon, 20 Aug 2007 14:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbook.com/blog/2007/08/16/links-for-2007-08-16/#comment-39585</guid>
		<description>This Hybrid Flash technology of yours, couldn&#039;t it be considered cloaking by Google (something they don&#039;t allow AFAIK)?

Stevie D</description>
		<content:encoded><![CDATA[<p>This Hybrid Flash technology of yours, couldn&#8217;t it be considered cloaking by Google (something they don&#8217;t allow AFAIK)?</p>
<p>Stevie D</p>
]]></content:encoded>
	</item>
</channel>
</rss>

