<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results for 'app:weblogs' matching tags 'Mindless Babbling' and 'Chrome'</title><link>http://msmvps.com/search/SearchResults.aspx?q=app:weblogs&amp;tag=Mindless+Babbling,Chrome&amp;orTags=0&amp;o=DateDescending</link><description>Search results for 'app:weblogs' matching tags 'Mindless Babbling' and 'Chrome'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Chrome's EULA</title><link>http://msmvps.com/blogs/williamryan/archive/2008/09/04/chrome-s-eula.aspx</link><pubDate>Thu, 04 Sep 2008 05:00:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1646761</guid><dc:creator>William</dc:creator><description>&lt;p&gt;Yah, I&amp;#39;m probably like the 10 trillionth person to post about it, but until now I hadn&amp;#39;t really had a chance to look at it. This morning &lt;a href="http://gizmodo.com/5044871/google-chrome-eula-claims-ownership-of-everything-you-create-using-chrome-from-blog-posts-to-emails"&gt;Gizmodo had a piece on it&lt;/a&gt; which definitely makes you shake your head thinking WTF. However like most things, I&amp;#39;m guessing that there&amp;#39;s a huge gulf between &amp;#39;reserving the right&amp;#39; to something and actually using that right.&amp;nbsp; Additionally, I&amp;#39;m guessing a lot of this is just legal CYA.&amp;nbsp; For instance, they could want access to information you post on a blog for efficiency purposes (being privy to it directly instead of having to crawl for it later) and just use language like this to avoid battles over the content.&amp;nbsp; Then again, i&amp;#39;m just speculating as I&amp;#39;m not a lawyer and have no clue.&lt;/p&gt; &lt;p&gt;I decided to search around and see how much was written about this and as of the time of this post, the terms &amp;quot;Chrome EULA Controversy&amp;quot; returned over 7,430 hits if taken together and well over 15k if you leave out the quotes.&amp;nbsp; And if you&amp;#39;ve been following this then you no doubt are aware that &lt;a href="http://arstechnica.com/news.ars/post/20080903-google-on-chrome-eula-controversy-our-bad-well-change-it.html"&gt;Google capitulated&lt;/a&gt; and is taking all the yucky stuff out.&amp;nbsp; If you&amp;#39;re trying to roll out a new product and have a big impact, then you definitely wouldn&amp;#39;t want the type of press Google was getting over this.&lt;/p&gt; &lt;p&gt;Their quick capitulation is some food for thought though. the most likely answer is that they didn&amp;#39;t really think they were doing anything bad b/c they weren&amp;#39;t intending to use it, it&amp;#39;s boilerplate etc etc. So it&amp;#39;s no sweat off of their backs to just get rid of it.&amp;nbsp; If you wanted to be conspiracy minded about it (I can only imagine for instance the &lt;a href="http://www.infowars.com/"&gt;Cow Alex Jones&lt;/a&gt; is going to have over it), it wouldn&amp;#39;t be hard to imagine that they threw it out there, willing to take it back but more than willing to use and abuse it if public outcry wasn&amp;#39;t too bad. I&amp;#39;m guessing there&amp;#39;s a small shred to that theory but little more.&lt;/p&gt; &lt;p&gt;All in all though, I think Chrome&amp;#39;s introduction is a good thing.&amp;nbsp; Firefox kicked off a ferocious battle that led to IE becoming a much better browser.&amp;nbsp; With another major player entering the market (and one that certainly has gotten under MS&amp;#39; skin when it comes to search), I&amp;#39;m guessing MS will pull some rabbits out of hats with IE 8 and when the dust settles, we&amp;#39;ll see some awesome functionality.&amp;nbsp; In the meantime, I like Chrome ok, but still sticking with IE for the foreseeable future.&lt;/p&gt;</description></item></channel></rss>