Have you seen Google News Custom Sections?
{ 0 comments }
Immediately after I posted about the Meebo Bar I decided to check out Google’s Real Time Search to gauge other people’s opinion of this new product from Meebo.
And I saw this…
This should relay the power of real time search and the importance of maintaining content outposts…
Meanwhile, Google Reader has yet to show any results…
UPDATE: Google Reader caught up between 7-1o minutes later…
{ 0 comments }
When I read the announcement today my first thought was “cool” – that’s good for everybody.
My next thought was of privacy and the implications of Google knowing absolutely everything I do online (as if they don’t already).
Here’s how this technology works… So DNS is what translates www.google.com into the IP address 74.125.45.100. It’s one of the underlying protocols that makes the internets work.
Why is that scary? If you bypass your ISP settings and setup Google Public DNS, Google becomes your gateway to the web.
This means every request you make to any website on the internet will pass through Google’s servers.
Are you ready for that? They’ll know when you go to Amazon.com or Facebook or Twitter. And since Google controls a vast market share of online advertising – you will start seeing advertising based on the websites you visit (p.s. you do already).
Here’s what Google says about the privacy of the Google Public DNS project…
We built Google Public DNS to make the web faster and to retain as little information about usage as we could, while still being able to detect and fix problems. Google Public DNS does not permanently store personally identifiable information.
What do you think about Google Public DNS? Better for the web as a whole? Or is this scary skynet stuff?
We’ll see….
{ 2 comments }
We talked about the Google Chrome OS launch a couple weeks ago and am finally getting around to reviewing it… I had troubles installing Google Chrome OS as a virtual machine in Windows but am now running it just fine – aside from a few crashes.
If you want to know what I think about Chrome OS right away… It’s meh.
First off – I got my Google Chrome OS Image from gdgt and am using VMWare’s VMPlayer to run the virtual machine. Some of my crashes may be the result of running it as a Virtual Machine so I won’t discount that in my Chrome OS experience.
So what is Chrome OS? Well, honestly … it’s just Google’s Chrome Browser, as you can see above. The only real difference is the dasboard (second image above) that links to web pages. Nothing special here.
And yep – that’s it! I was expecting something more exciting but it really is just the browser. Don’t get me wrong – I live in the browser but there are so many other things you realize you do when you are limited to just a browser. This is what Sergey wants – to keep it simple.
But this is too simple and really only fits the netbook market. There is no way I could run Google Chrome OS as my main operating system on my workstation or laptop. I could see running this on a netbook where you pretty much only need a browser.
As is – this will never compete directly with Windows and OSX. In this current iteration it’s only usable on netbooks. I was hoping for something revolutionary but got something overly simple. I expected to spend a couple hours reviewing it but it only took 10 minutes.
It’s a browser people – that’s it.
{ 0 comments }
I downloaded Google Chrome OS from GDGT but had problems installing it per their instructions….
Here’s what I found through discussions on how to install Google Chrome OS on Windows with VMWare Player
1) Create a folder on your C drive called Virtual Machines
2) Download the Chromium image from Gdgt and extract the VMDK file to c:\Virtual Machines
3) Download and Install VMWare Player
4) In VMWare Player…
a. Select “Create a New Virtual Machine”
b. Select “I will install the operating system later” and click the Next button
c. Under Guest Operating System select Other and under Version select Other and click the Next button
d. Under Virtual Machine Name enter “Chrome OS” and under Location browse to the c:\Virtual Machines folder you created above and click the Next button. [Note: This will be the downloaded VMDK file and the newly created blank Virtual Machine in the same folder]
e. On the Specify Disk Capacity page leave defaults as they are and click the Next button.
f. On the Ready to Create Virtual Machine page click the Finish button.
5) Navigate to the c:\Virtual Machines folder in Windows Explorer.
a. Rename Chrome OS.vmdk to Chrome OS.vmdk.old
b. Rename chrome-os-0.4.22.8-gdgt.vmdk to Chrome OS.vmdk
6) On the VMWare Player main screen select Chrome OS and click Play Virtual Machine [Note: This will show the OS logon screen]
7) In the bottom right hand corner of the VMWare Player window right click on the Network Adapter Icon and click Disconnect then select Settings.
8) On the Virtual Machine Settings window on the right hand side under Network connection select Bridged and then click the OK button.
9) In the bottom right hand corner of the VMWare Player window right click on the Network Adapter Icon and click Connect
10) On the OS logon screen enter your Google e-mail address as your username and your Google password as your password.
{ 0 comments }
