I was shocked last month when Google dropped the beta designation from Chrome. Chrome was in beta a mere three months, whereas some products such as Gmail are STILL in beta after more than four years! Sometimes I just don’t understand why they do weird things like this, but it’s really all just semantics.
I’ve been finding myself searching Twitter for information as of late. There was not a decent Twitter search button for the Google Toolbar (only a couple that use the Google Custom Search Engine), so I created one. It’s simple and easy to use, just like my Google Reader search button.
- Click the link below to install it
- When you want to search Twitter, type a search term into your Google Toolbar
- Click the Twitter button on the Google Toolbar
- You are taken to the Twitter search result page for your search term
Install the Twitter Search Button
Why the Google Toolbar does not include a search button for Google Reader by default is beyond me! I searched for a Google Reader button in the button gallery, and much to my dismay the only one I found does not perform a search. I then took it upon myself to create my own search button for Google Reader. If you search your reader items as much as I do, you’re going to love it!
Install the Google Reader search button
When Firefox 3 was officially released, the Google Toolbar was not supported. Of course, that didn’t stop me from manually updating the MaxVerison myself so that it would work. Although it didn’t take long for Google to release a new version that officially supported Firefox 3, I was disappointed as there were no new features to be found. It seems all they really did was update the MaxVersion as I had already done.
If you would like to use Google Chrome at work, but are unable because you have a SOCKS proxy, you’re not alone. It is a known issue that Chrome does not work with socks. Initially I couldn’t even install Chrome because of my firewall at work. I did install it on my laptop when I got home the day it came out. However, when I came back to work the next day I was disappointed to learn that it didn’t work behind a SOCKS proxy.