<?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: Google thinks Google may harm your computer??</title>
	<atom:link href="http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/</link>
	<description>more from postalnews.com</description>
	<lastBuildDate>Wed, 08 Feb 2012 21:55:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Randy B.</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-135492</link>
		<dc:creator>Randy B.</dc:creator>
		<pubDate>Tue, 23 Jun 2009 17:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-135492</guid>
		<description>I&#039;m definitely bookmarking this site.  Really great articles.  Do you recommend any other readings?</description>
		<content:encoded><![CDATA[<p>I&#8217;m definitely bookmarking this site.  Really great articles.  Do you recommend any other readings?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joleen</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-128810</link>
		<dc:creator>Joleen</dc:creator>
		<pubDate>Wed, 04 Feb 2009 21:29:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-128810</guid>
		<description>check the folowing link
nicholas carrier to me 
show details 2:36 PM (1 hour ago) Reply


Here is the link explaining it - http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html</description>
		<content:encoded><![CDATA[<p>check the folowing link<br />
nicholas carrier to me<br />
show details 2:36 PM (1 hour ago) Reply</p>
<p>Here is the link explaining it &#8211; <a href="http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html" rel="nofollow">http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joleen</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-128807</link>
		<dc:creator>Joleen</dc:creator>
		<pubDate>Wed, 04 Feb 2009 20:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-128807</guid>
		<description>This Blog Google Blogs Web Blog News 
This Blog
     

Google Blogs
     

Web
     

Blog
      


News
      


&quot;This site may harm your computer&quot; on every search result?!?!
 
1/31/2009 09:02:00 AM 
If you did a Google search between 6:30 a.m. PST and 7:25 a.m. PST this morning, you likely saw that the message &quot;This site may harm your computer&quot; accompanied each and every search result. This was clearly an error, and we are very sorry for the inconvenience caused to our users.

What happened? Very simply, human error. Google flags search results with the message &quot;This site may harm your computer&quot; if the site is known to install malicious software in the background or otherwise surreptitiously. We do this to protect our users against visiting sites that could harm their computers. We maintain a list of such sites through both manual and automated methods. We work with a non-profit called StopBadware.org to come up with criteria for maintaining this list, and to provide simple processes for webmasters to remove their site from the list.

We periodically update that list and released one such update to the site this morning. Unfortunately (and here&#039;s the human error), the URL of &#039;/&#039; was mistakenly checked in as a value to the file and &#039;/&#039; expands to all URLs. Fortunately, our on-call site reliability team found the problem quickly and reverted the file. Since we push these updates in a staggered and rolling fashion, the errors began appearing between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m., so the duration of the problem for any particular user was approximately 40 minutes.

Thanks to our team for their quick work in finding this. And again, our apologies to any of you who were inconvenienced this morning, and to site owners whose pages were incorrectly labelled. We will carefully investigate this incident and put more robust file checks in place to prevent it from happening again.

Thanks for your understanding.</description>
		<content:encoded><![CDATA[<p>This Blog Google Blogs Web Blog News<br />
This Blog</p>
<p>Google Blogs</p>
<p>Web</p>
<p>Blog</p>
<p>News</p>
<p>&#8220;This site may harm your computer&#8221; on every search result?!?!</p>
<p>1/31/2009 09:02:00 AM<br />
If you did a Google search between 6:30 a.m. PST and 7:25 a.m. PST this morning, you likely saw that the message &#8220;This site may harm your computer&#8221; accompanied each and every search result. This was clearly an error, and we are very sorry for the inconvenience caused to our users.</p>
<p>What happened? Very simply, human error. Google flags search results with the message &#8220;This site may harm your computer&#8221; if the site is known to install malicious software in the background or otherwise surreptitiously. We do this to protect our users against visiting sites that could harm their computers. We maintain a list of such sites through both manual and automated methods. We work with a non-profit called StopBadware.org to come up with criteria for maintaining this list, and to provide simple processes for webmasters to remove their site from the list.</p>
<p>We periodically update that list and released one such update to the site this morning. Unfortunately (and here&#8217;s the human error), the URL of &#8216;/&#8217; was mistakenly checked in as a value to the file and &#8216;/&#8217; expands to all URLs. Fortunately, our on-call site reliability team found the problem quickly and reverted the file. Since we push these updates in a staggered and rolling fashion, the errors began appearing between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m., so the duration of the problem for any particular user was approximately 40 minutes.</p>
<p>Thanks to our team for their quick work in finding this. And again, our apologies to any of you who were inconvenienced this morning, and to site owners whose pages were incorrectly labelled. We will carefully investigate this incident and put more robust file checks in place to prevent it from happening again.</p>
<p>Thanks for your understanding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-128806</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Wed, 04 Feb 2009 19:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-128806</guid>
		<description>It was the result of human error. Here is the link explaining it. - http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html</description>
		<content:encoded><![CDATA[<p>It was the result of human error. Here is the link explaining it. &#8211; <a href="http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html" rel="nofollow">http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amused</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-128779</link>
		<dc:creator>Amused</dc:creator>
		<pubDate>Sat, 31 Jan 2009 15:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-128779</guid>
		<description>This is amusing, though not so much for monetized websites.</description>
		<content:encoded><![CDATA[<p>This is amusing, though not so much for monetized websites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Metablocks &#124; This site may harm your computer - Google on the Blink?! - Widget and Facebook App Development and Design</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-128778</link>
		<dc:creator>Metablocks &#124; This site may harm your computer - Google on the Blink?! - Widget and Facebook App Development and Design</dc:creator>
		<pubDate>Sat, 31 Jan 2009 15:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-128778</guid>
		<description>[...] Postal News Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Postal News Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laron</title>
		<link>http://www.postalnewsblog.com/2009/01/31/google-thinks-google-may-harm-your-computer/comment-page-1/#comment-128777</link>
		<dc:creator>Laron</dc:creator>
		<pubDate>Sat, 31 Jan 2009 15:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.postalnewsblog.com/?p=1421#comment-128777</guid>
		<description>I got that problem too. Im glad im not the only one</description>
		<content:encoded><![CDATA[<p>I got that problem too. Im glad im not the only one</p>
]]></content:encoded>
	</item>
</channel>
</rss>

