<?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>Daniel Hall&#039;s Website &#187; Google</title>
	<atom:link href="http://www.danielhall.me/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.danielhall.me</link>
	<description>Because the Internet doesn&#039;t have enough opinions already</description>
	<lastBuildDate>Thu, 29 Jul 2010 11:52:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Google&#8217;s Privacy Bungle</title>
		<link>http://www.danielhall.me/2010/06/googles-privacy-bungle/</link>
		<comments>http://www.danielhall.me/2010/06/googles-privacy-bungle/#comments</comments>
		<pubDate>Sat, 05 Jun 2010 03:37:27 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Wifi]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=621</guid>
		<description><![CDATA[<p>Google has recently taken a large amount of criticism for capturing  unencrypted wireless network traffic as part of its Street View project.  Google admitted to the world that although it was only looking to  capture station MAC addresses it inadvertently also captured the payload  data. Many articles have emerged blasting Google [...]]]></description>
			<content:encoded><![CDATA[<p>Google has recently taken a large amount of criticism for capturing  unencrypted wireless network traffic as part of its Street View project.  Google admitted to the world that although it was only looking to  capture station MAC addresses it inadvertently also captured the payload  data. Many articles have emerged blasting Google for what Senator  Conroy calls &#8216;This is probably the single greatest breach in the history of privacy&#8217;. I believe Google hasn&#8217;t done all that wrong, to  understand why you need to know how a wireless network works.</p>
<p>Wireless networks can either be encrypted or unencrypted but in both  these cases only the payload is encrypted. The packet headers which  contain information about who the packet is addressed to and who it is  from. The reasons for this are similar to why you might write a letter  in code, but you would not write the envelope in code. In an unencrypted  network the whole packet is sent in clear text including the envelope  and contents. The difference between these analogies and how a real  network works though is that to read the envelope you need to physically  obtain it and there is only one copy. A wireless network broadcasts  everything to everyone within 100 meters.</p>
<p>This isn&#8217;t really a problem if your network is encrypted as people will  not be able to read it easily. If however your network is not encrypted  its the equivalent of yelling out everything that you type into and read  from your PC. Almost all banking websites will ask your PC to use extra  encryption, but many other sites will not. So anyone in a 100 meter  range of your computer or access point can watch everything you do on  your computer.</p>
<p>What Google were trying to do was get a list of the locations of these  access points. So they would have captured the headers of all packets  they saw, grabbed the wireless routers address out of it and marked its  location on a map. Except according to them they accidentally put code in  that captured the whole packet. This meant that for all the unencrypted  networks the Google Street View cars drove past they may have captured  private information.</p>
<p>There is a class action in Germany against Google for capturing this  data, and more can be expected elsewhere soon. Suing Google for this is  like walking in to a public place, yelling out a bunch of private  information and then suing anyone who happened to be recording at the  time, or suing someone for writing down smoke signals you send to someone from the top of a mountain. If your  access point is sending data unencrypted then every wireless device  within 100 meters cannot help but hear your data, you&#8217;re just lucky most  will ignore it.</p>
<p>If you really cared about your privacy you would at least make some  attempt to restrict others access to your data. Not knowing is much an  excuse as not knowing people were recording in that shopping mall. Don&#8217;t  take your privacy for granted, check whether your network is encrypted,  and if you don&#8217;t know how, get someone who does. Ignorance is not an  excuse! This time it was Google, the next time it could be an identity  thief.</p>
<p><strong>Random Thought:</strong> If privacy is so important to people at the moment, what&#8217;s with all the data on Facebook?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2010/06/googles-privacy-bungle/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Google G1: Six Months On</title>
		<link>http://www.danielhall.me/2010/03/google-g1-six-months-on/</link>
		<comments>http://www.danielhall.me/2010/03/google-g1-six-months-on/#comments</comments>
		<pubDate>Wed, 31 Mar 2010 09:20:09 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[SSH]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=559</guid>
		<description><![CDATA[<p>So six months ago I bought my Google G1, my first impressions were excited and extremely positive. Has this phone stood the test of time though?</p>
Physically
<p>The phone is still in good physical condition, which is more than I could have said about my old XDA Atom Flame after six months. There are a few scratches [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-weight: normal;">So six months ago I bought my Google G1, my first impressions were excited and extremely positive. Has this phone stood the test of time though?</span></p>
<h1>Physically</h1>
<p>The phone is still in good physical condition, which is more than I could have said about my old XDA Atom Flame after six months. There are a few scratches on the screen, but I bought a screen protector for it so I can simply peel them off. Surprisingly the various crevices on the phone have avoided build ups of dust which commonly plagues my phones. The battery is beginning to fade, and can only last me around 12 hours with my ordinary usage (which is probably considered heavy usage). This makes weekends away from home interesting as I have to avoid using my phone to stretch the battery over 24 hours.</p>
<p>When I first got the phone I expected that the keyboard keys would fade, or that the keyboard snap mechanism would somehow break. I was wrong, the keys are still as visible as when I first got it, and the snap mechanism still works perfectly.</p>
<h1>The OS</h1>
<p>In the time I&#8217;ve had this phone Android has gone from 1.1 to 2.0. Sadly there haven&#8217;t been any official new releases of the phone software. There have however been releases of the well known mod for this phone called &#8216;CyanogenMod&#8217;. Currently CyanogenMod is at Android version 1.5 with parts of 2.0 ported across.</p>
<p>Since the first week I had the phone I&#8217;ve been using CyanogenMod and have seen the improvements in it take it from strength to strength. Originally it looks almost the exact same as the original OS but now it includes several features that I could not live without. My favorites would be:</p>
<ul>
<li>Tethering to my Linux PC</li>
<li>OpenVPN settings</li>
<li>360 degree rotation</li>
<li>Improved contacts screen with direct call links</li>
<li>Voice Search</li>
</ul>
<h1>The Applications</h1>
<p>Like any mobile OS the best part is the applications. This is where an OS either make it or breaks it. While Google have been constantly improving the Android platform old apps have remained around and stayed compatible with the phone. Google has also held two developer competitions during the time I&#8217;ve had the phone which has brought loads of new apps and innovation. So as each application is its own entity I&#8217;m going to review my favorites separately.</p>
<h2>Google Maps</h2>
<p>When I got the phone Google Maps was simply a map, with limited search capability and able to give directions. Since then however Google have added Street View, Navigation (US Only sadly), Buzz and much better searching. For something I used once a month I now use it almost daily.</p>
<h2>ConnectBot</h2>
<p>One of the reasons I went for a phone with a hardware keyboard was to make SSHing into my Linux machines easier. ConnectBot handles this perfectly. I cannot stress enough how useful this application is. Recently it has been improved to include support for SSH agents too which improved things even further.</p>
<h2>My Tracks</h2>
<p>As someone who enjoys hiking and walking having a GPS logger can be extremely useful. My Tracks basically turns your Android phone into a GPS logger and displays the data for you on a map. It also allows you to export the logs in popular formats or simply upload them to My Maps on Google. It can also graph your elevation, speed and display interesting statistics.</p>
<h1>Conclusion</h1>
<p>All up I still enjoy this phone, and still use it daily. I am looking at moving to either an N900 or the Google Nexus One next. I haven&#8217;t moved because the N900 has been having trouble with the USB connectors breaking off, and the Nexus One is too expensive to import into Australia. I doubt I&#8217;ll be moving to another phone any time soon and this phone doesn&#8217;t look like it will give out any time in the near future.</p>
<p><strong>Random Thought:</strong> What is the cell phone market going to look like five years from now? And where the hell is my wristwatch phone?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2010/03/google-g1-six-months-on/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Google C&amp;Ds CyanogenMod</title>
		<link>http://www.danielhall.me/2009/09/google-cds-cyanogenmod/</link>
		<comments>http://www.danielhall.me/2009/09/google-cds-cyanogenmod/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 03:23:16 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=371</guid>
		<description><![CDATA[<p>In an act that appears to contradict both the &#8216;do no evil&#8217; and the &#8216;android is open&#8217; mantras of Google they sent a Cease and Desist to CyanogenMod creator Cyanogen. This effectively means that all cooked versions can now no longer include and Google applications, sync with Google services or the many other closed source [...]]]></description>
			<content:encoded><![CDATA[<p>In an act that appears to contradict both the &#8216;do no evil&#8217; and the &#8216;android is open&#8217; mantras of Google they sent a Cease and Desist to CyanogenMod creator Cyanogen. This effectively means that all cooked versions can now no longer include and Google applications, sync with Google services or the many other closed source parts of the ROM. I use Cyanogen&#8217;s mod and this effectively cripples it to a worthless Linux phone distribution. Google have essentially said to me &#8220;You know that T-Mobile G1 you brought that was supposed to be completely open? Well we never made all the good bits open, and now we&#8217;re taking them away.&#8221;. I can&#8217;t use the Official ROM because I live in Australia and it constantly sends text messages to T-Mobiles myFaves which costs me a fortune. So Google has removed my ability to use their services on my &#8216;Google&#8217; phone. So now wherever you read a press release where Google claims that Android is open you know what they really mean is they made the stuff they had to open and closed the rest.</p>
<p>I see only one way out of this mess, we need developers to replace all the closed source parts of Android with free software solutions. This means Android will be free and fully open source. Why stop there though? Lets make Google&#8217;s decision into one they will regret! As the open source community is replacing the closed source apps we should build in functionality to allow the phone to work with Google&#8217;s competitors. When you first used the G1 you had to sign in using your Google account. What if that same box let you sing in with your Live Id, your Yahoo account or even OpenID? Imagine the Android phone being written in completely open source to work on any operator! It wouldn&#8217;t be hard either, most are beginning to provide APIs to their accounts and I&#8217;m sure they&#8217;d love to help.</p>
<p>Edit: According the the Save Cyanogen Petition application on the market it is impossible to even run the ROMs that Google claim to support without the Google binaries.</p>
<p><strong>Random Thought:</strong> Did you know the <a href="http://www.csse.unimelb.edu.au/dept/about/csirac/">first Australian computer</a> was built by <a href="http://www.csse.unimelb.edu.au/dept/about/csirac/designer.html">Trevor Pearcey</a> and <a href="http://www.csse.unimelb.edu.au/dept/about/csirac/designer.html">Maston Beard</a> in 1947-1951.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2009/09/google-cds-cyanogenmod/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The T-Mobile G1 Phone</title>
		<link>http://www.danielhall.me/2009/09/the-t-mobile-g1-phone/</link>
		<comments>http://www.danielhall.me/2009/09/the-t-mobile-g1-phone/#comments</comments>
		<pubDate>Sat, 19 Sep 2009 07:54:57 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=354</guid>
		<description><![CDATA[<p>The T-Mobile G1 Phone goes by a few names. HTC Dream and Google Android Development phone are two more. Essentially they are the same hardware and the only change is the software. The Android Development phone unlike the others comes with an unlocked bootloader allowing you to flash any software image you want where the [...]]]></description>
			<content:encoded><![CDATA[<p>The T-Mobile G1 Phone goes by a few names. HTC Dream and Google Android Development phone are two more. Essentially they are the same hardware and the only change is the software. The Android Development phone unlike the others comes with an unlocked bootloader allowing you to flash any software image you want where the other two will only allow software signed by either HTC or T-Mobile.</p>
<p>I bought mine two weeks ago and it has completely replaced my Windows Mobile phone to the point where I actually gave it away. The main issues that I have with Windows Mobile was the instability and the difficult to use interface. This new phone was a breath of fresh air. Amazingly when I was testing it out with the seller it received a weeks worth of SMSes indicating that my Windows Mobile phone had stopped accepting them.</p>
<p>I opted for the T-Mobile option. Mainly because I found one cheap on eBay but also because I knew of an exploit to easily get root, flash a new bootloader and install whatever OS I wanted. I knew with almost absolute certainty that I would want to be able to play with root access to the OS. I could have went with the HTC Hero or Magic (the successors to the G1) but I liked the idea of the flip out keyboard way too much.</p>
<p>The G1 is easy to use without a stylus, in fact it won&#8217;t work with a stylus as is uses a capacitive touch screen. This means all the applications, the keyboard and the core OS are designed with that in mind. While I could use my old phone with my thumbs many of the controls were impossible to use without perfect precision. Generally all the controls on the Andriod are larger and easier to manipulate, where the Windows Mobile controls are clunky and small.</p>
<p>The Android marketplace is also something that Windows Mobile could certainly have done with. It is an almost perfect image of the iPhone App Store, except that in the culture of open source most of the applications are free. The applications are easier to search for, review and download making the Android Marketplace a much easier to use and more polished tool.</p>
<p>One thing this phone and my last one have in common was the hacker community around them. Both have multiple ROMs available and its relatively easy to flash a new one. I&#8217;m currently running the latest stable CyanogenMod (4.0.4) which was extremely easy to flash courtesy of the latest kernel vulnerability and some specially designed tools.</p>
<p><strong>Random Thought:</strong> I thought Androids could make breakfast for me.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2009/09/the-t-mobile-g1-phone/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s New Search Engine</title>
		<link>http://www.danielhall.me/2009/09/googles-new-search-engine/</link>
		<comments>http://www.danielhall.me/2009/09/googles-new-search-engine/#comments</comments>
		<pubDate>Sat, 12 Sep 2009 00:00:53 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[The Internet]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Review]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=255</guid>
		<description><![CDATA[<p>Thanks to a post by my friend Daryl, I&#8217;ve been looking at the improved Google search engine, codenamed Caffeine. Google has had a bunch of competition lately. Bing which is Microsoft&#8217;s new search engine recently launched, followed by an announcement that Yahoo will use Bing as its engine.</p>
<p>The current version of Google updates its index [...]]]></description>
			<content:encoded><![CDATA[<p>Thanks to <a href="http://darylteo.com/blog/2009/08/12/google-2-0/">a post by my friend Daryl</a>, I&#8217;ve been looking at the improved Google search engine, codenamed Caffeine. Google has had a bunch of competition lately. Bing which is Microsoft&#8217;s new search engine recently launched, followed by an announcement that Yahoo will use Bing as its engine.</p>
<p>The current version of Google updates its index on a schedule. This means that sites that have only just been crawled will have to wait a while before being included in search results. I have experienced this with my site, only recently has Google started giving me hits, although they have been crawling my site for about a month.</p>
<p>Google&#8217;s new search engine use a new backend which not only improves the time required to perform a search but allows indexes to be easily updated. This means Google can now include real time sensitive results such as those from twitter or from my blog minutes after I post. This means that instead of searching the web of about an hour ago you are now searching what is on the web now.</p>
<p>Effectively Google is making a real time search engine. Where informatin is avaliable to you as it happens. Imagine the implications of having an auto updating search results page where new results dynamically appear as they are posted. This is thereason why Google is pushing the Pubsubhubbub protocol and blog pinging services.</p>
<p><strong>Random Thought:</strong> Google Androids wpToGo application makes it easy to post from my mobile, but it&#8217;s a bit of a pain in the thumbs.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2009/09/googles-new-search-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The New Google Reader</title>
		<link>http://www.danielhall.me/2009/07/the-new-google-reader/</link>
		<comments>http://www.danielhall.me/2009/07/the-new-google-reader/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 20:17:30 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[The Internet]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Reader]]></category>
		<category><![CDATA[Review]]></category>
		<category><![CDATA[RSS]]></category>
		<category><![CDATA[Social Networking]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=98</guid>
		<description><![CDATA[<p>This morning Google announced some new features for Google Reader. These features make Reader feel like a social networking website. I think Google is taking an interesting approach to social networking. They&#8217;re refitting all their existing products to include social features. It still feels a little separate though. There isn&#8217;t a feel of congruency across [...]]]></description>
			<content:encoded><![CDATA[<p>This morning Google <a href="http://googlereader.blogspot.com/2009/07/following-liking-and-people-searching.html">announced some new features</a> for Google Reader. These features make Reader feel like a social networking website. I think Google is taking an interesting approach to social networking. They&#8217;re refitting all their existing products to include social features. It still feels a little separate though. There isn&#8217;t a feel of congruency across all the applications.</p>
<p>You can now decide who sees your shared items, and who can comment on them. I don&#8217;t see this as a feature I&#8217;d likely use as everything I share is already on the web and if I block people from seeing it on my shared items then they can just find it elsewhere. I have a feeling that Google did this to fight off the hordes of people yelling loudly about privacy lately.</p>
<p>Google Reader now displays information from your profile and a link to your fully profile at the top of your shared items page. What you can store on your Google Profile appears akin to what you can store on other social networking sites. A link to your profile is kind of a different approach to social networking. Sites lik<img class="alignright size-full wp-image-122" title="RSS Feed Icon" src="http://www.danielhall.me/wp-content/uploads/2009/07/feed-icon-128x128.png" alt="RSS Feed Icon" width="128" height="128" />e Facebook and MySpace focus on your profile and links to other features. Google&#8217;s approach seems to be to add social features to all their applications and link that to a profile. This approach seems to me to be the best way to muscle in on the social networking scene.</p>
<p>Google Reader now includes a button to &#8216;like&#8217; a post. This is the most controversial features as it adds an extra line to the post and takes up a fair bit of screen real estate. I don&#8217;t notice it taking up too much space, that could either be due to the fact I&#8217;m used to having a small screen on my laptop and on my desktop my monitor is big enough for me to not notice. I think the idea is great, you can easily find people who like the same things you do and follow them. The only issue i have with it right now is that everyone is clicking like on everything and there are way too many people to sort through to find somebody with similar interests.</p>
<p>This is an interesting approach for Google, but i believe it will pay off. Google is creating a social network that isn&#8217;t about having friends or getting the most views. Google&#8217;s social network is about people similar to you and things you like.</p>
<p><strong>Random thought:</strong> Punishment in real life: You perform an illegal operation and you go to jail, Punishment in computing: You perform an illegal operation and you get killed.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2009/07/the-new-google-reader/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Obligatory Post on Google Chrome OS</title>
		<link>http://www.danielhall.me/2009/07/the-obligatory-post-on-google-chromeos/</link>
		<comments>http://www.danielhall.me/2009/07/the-obligatory-post-on-google-chromeos/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 01:54:08 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.danielhall.me/?p=54</guid>
		<description><![CDATA[They keep mentioning simplicity, lightweight and 'back to the basics'. have you ever used an OS designed to be extremely simple? Have you ever tried SplashTop, HyperSpace, Latitude ON or even gOS? They may be fast to start up, but you'll curse just as much when the one thing you want to do is only possible on the actual OS you have installed, requiring a reboot. My opinion is that these lightweight OSes actually make my life [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m not excited by Google Chrome OS. And the majority of the reason for that stems from the following paragraph posted on the <a href="http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html" target="_self">Official Google Blog</a>:</p>
<blockquote><p>Speed, simplicity and security are the key aspects of Google Chrome OS. We&#8217;re designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don&#8217;t have to deal with viruses, malware and security updates. It should just work.</p></blockquote>
<p>They keep mentioning simplicity, lightweight and &#8216;back to the basics&#8217;. have you ever used an OS designed to be extremely simple? Have you ever tried SplashTop, HyperSpace, Latitude ON or even gOS? They may be fast to start up, but you&#8217;ll curse just as much when the one thing you want to do is only possible on the actual OS you have installed, requiring a reboot. My opinion is that these lightweight OSes actually make my life harder. Lets see one use case.</p>
<p>I&#8217;m at home and I need to check my email. This can be done in ExpressGate so I boot it up (really fast) open up a browser and browse to my Gmail. So far the experience is relatively smooth, until I discover that somebody has sent me an attachment that I need to see. Of course this requires an application installed in my OS so I have to close my browser and any other sites I had open and wait for a reboot into my OS. This is the inherent problem, if I need to use something that isn&#8217;t part of my lightweight distribution then I have to stop everything and wait.</p>
<p>Now I understand Google Chrome OS is going to be the actual OS, except most of the applications will be based in the cloud. This presents another problem, especially on netbooks. Netbooks are portable, and designed to be used in places where there is no internet connection. See the problem? Sure you could use a 3G modem but then you have to fork out a fortune for data (especially excess usage).</p>
<p>Unless Google can find a creative way to solve these problems I don&#8217;t think that Chrome OS will be anything exciting. It should be noted though that if I were to pick a company that would be able to take on this challenge I would pick Google. I suppose in the end there is only one way to find out, and that would be to wait until the end product is released.</p>
<p><strong>Random thought:</strong> If you use a Live CD of another distribution, but don&#8217;t install it, is it still cheating?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.danielhall.me/2009/07/the-obligatory-post-on-google-chromeos/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
