<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mike Design &#187; Google</title>
	<atom:link href="http://www.mikedesign.net/category/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikedesign.net</link>
	<description>The Ramblings of a Web Developer...</description>
	<lastBuildDate>Thu, 11 Jun 2009 19:40:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Google Goofs!</title>
		<link>http://www.mikedesign.net/2009/02/02/google-goofs/</link>
		<comments>http://www.mikedesign.net/2009/02/02/google-goofs/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 14:38:07 +0000</pubDate>
		<dc:creator>Mike Auteri</dc:creator>
				<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.mikedesign.net/?p=84</guid>
		<description><![CDATA[
If  you&#8217;re anything like me, you get up early on Saturday morning and go straight to your computer. What? You don&#8217;t do that. Oh, well in that case, you probably missed all the excitement this past Saturday. Okay, it&#8217;s not very exciting, but interesting at least.
As I was building a new form for a site, [...]]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-87 alignright" title="google_fail" src="http://www.mikedesign.net/wp-content/uploads/2009/02/google_fail.jpg" alt="google_fail" width="276" height="185" /></p>
<p>If  you&#8217;re anything like me, you get up early on Saturday morning and go straight to your computer. What? You don&#8217;t do that. Oh, well in that case, you probably missed all the excitement this past Saturday. Okay, it&#8217;s not very exciting, but interesting at least.</p>
<p>As I was building a new form for a site, I was interrupted by a fellow web developer via Google chat. &#8220;Dude,&#8221; he said. &#8220;Have you seen Google?&#8221; Quickly, I pointed my browser Google-bound to see what in heck he was talking about. Turned out, every site had the warning <strong>This site may harm your computer</strong>.</p>
<p><span id="more-84"></span>Well, that isn&#8217;t good, I thought. I guess even Google still has humans working for them. How old fashion&#8230;</p>
<p>Here is the <a title="Google" href="http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html" target="_blank">explanation</a> Google released shortly after fixing the problem on their blog:</p>
<blockquote><p>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 “This site may harm your computer” 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 “This site may harm your computer” 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 work with a non-profit called StopBadware.org to get our list of URLs. StopBadware carefully researches each consumer complaint to decide fairly whether that URL belongs on the list. Since each case needs to be individually researched, this list is maintained by humans, not algorithms.</p>
<p>We periodically receive updates to that list and received one such update to release on the site this morning. Unfortunately (and here’s the human error), the URL of ‘/’ was mistakenly checked in as a value to the file and ‘/’ 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>
<p>Posted by Marissa Mayer, VP, Search Products &amp; User Experience</p></blockquote>
<p>I only had to do one search that morning. Fortunately, <a title="Yahoo!" href="http://www.yahoo.com/" target="_blank">Yahoo!</a> was still in good shape.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mikedesign.net/2009/02/02/google-goofs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Reader My Lips: Brand New Feature</title>
		<link>http://www.mikedesign.net/2008/12/05/google-reader-my-lips-brand-new-feature/</link>
		<comments>http://www.mikedesign.net/2008/12/05/google-reader-my-lips-brand-new-feature/#comments</comments>
		<pubDate>Fri, 05 Dec 2008 04:11:08 +0000</pubDate>
		<dc:creator>Mike Auteri</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Google Reader]]></category>

		<guid isPermaLink="false">http://www.mikedesign.net/?p=64</guid>
		<description><![CDATA[This evening I came home from a long day of work to find my wife sobbing at her computer&#8230; okay, that&#8217;s not true. BUT, she was quite upset. Because today, Google redesigned the front-end of its fairly popular web-based aggregator, Google Reader, and she was less than thrilled about it.
&#8220;I liked the way it was before! [...]]]></description>
			<content:encoded><![CDATA[<p>This evening I came home from a long day of work to find my wife sobbing at her computer&#8230; okay, that&#8217;s not true. BUT, she was quite upset. Because today, <a title="Google" href="http://www.google.com/" target="_blank">Google</a> redesigned the front-end of its fairly popular web-based aggregator, <a title="Google Reader" href="http://www.google.com/reader" target="_blank">Google Reader</a>, and she was less than thrilled about it.</p>
<blockquote><p>&#8220;I liked the way it was before! I was used to it! Why did they have to change it! Why! WHY! WHHHHY!&#8221; She said.</p></blockquote>
<p>It seemed similar to the many that ranted about the new <a title="Facebook" href="http://www.facebook.com/" target="_blank">Facebook</a> face-lift a few months ago. Though, I think that one was a bit more warranted since it actually made the site more confusing to navigate. Anyway, I digress.</p>
<p>Personally, I like the new Reader look. Actually, the only thing that appears different (to me, at least, but I have a bad memory when it comes to things like this. I actually didn&#8217;t even notice that Facebook changed until someone pointed it out) is the left-side column which now has categories that can be expanded and collapsed. Makes it look a lot cleaner if you ask me. Plus, I can play with that new aspect of the site when I get bored!</p>
<p>Anyway, Steph (that&#8217;s my wife) actually admitted that most of the people were blogging that they liked the new Google Reader look. She apparently is in the minority. Well, sorry honey, I agree with the masses on this one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mikedesign.net/2008/12/05/google-reader-my-lips-brand-new-feature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
