I recently picked up some domains for my next open source project - G+ Notifier. It's a simple Windows utility that'll sit in the notification area and alert you to notifications from Google+! Similar to my previous Google Wave Notifier, but hopefully Google won't discontinue this service quite so quick!

I'm not sure if I'll be able to launch the application before Google+ gets a public API, but I'll do some investigation over the coming days.

If you want to be kept informed with the progress of the app, please follow G+ Notifier on Google+, I'll post all updates on that account :-)

The website for the application is gplusnotifier.com and will also be updated regularly. Full source code will be hosted on Bitbucket!

I hate Twitter.

It's always down, it's full of spambots, and 140 characters is just too short. If I find myself going back to shorten words to cram them in, then there's something wrong. It can't be my fault - I don't know any big words!

With that out of the way, hopefully it's clear I'm a Twitter Fanboi. Infact, you could probably conclude that I'm a Google Fanboi. I host my domains at Google, I use their email (Apps for Domain - all free!), I even wrote this blog in Python - a language I've never used before, to host on App Engine. I'm a Google Trusted tester, and have been beta testing new features in Buzz for a few months. I'd go and work for Google at the drop of a hat.

Hate Twitter, Love Google, but Ditching Buzz? WTF?

It might sound a bit crazy, but there are good reasons. And in the interests of being constructive, I'm going to list them here. Some of them might (will) contradict things said above, but tough. That's how it is.

• Not enough people using it. It's catch 22, but all the people I want to follow do not use Buzz, so I have to use Twitter too. I don't need two services doing (mostly) the same thing.
• Posts are too long. This might sound stupid given I said Twitter was too short, but the problem with Buzz is that it takes too long to catch up with things. I should be able to skip over a summary of posts, with a link to read more for the things that entice me. Twitter got the number of characters wrong, but the idea of restricting things right. I can skim over 24 hours of Twitter in 5 minutes. Not true of Buzz.
• Google Buzz still can't sort properly. This one really bugs me. Googlers suggested muting, but this is a pain in the ass, and will also break Google's clever algorithm that learns what I want to read. I want to read it - I just don't want comments sending it to the top!
• There are no decent iPad clients. I love Twitterrific on my iPad. Buzz doesn't have any decent clients (seemingly on any platform). I don't like web-based apps, they just aren't written to work with the device, and they're slow. I totally get that Google want to be web-based and work on all platforms. That really is great - but they will definitely lose out a little against clients written specifically for a device.

Some of these reasons are linked - eg. a decent client would surely sort properly :-) However, one of the problems that a third party can't solve is that it's impossible to render a decent "summary" of a Buzz post. The web application shows the first few lines, but this rarely represents the content of the article.

I totally believe Google Buzz could easily become a better service than Twitter (Apples to Oranges, I know, but there isn't really need for both). Unfortunately it has some major issues that just make it hard for me to use. It's entirely possible that my use case is wrong, and that it's a fantastic service for other people. For me, however, it just doesn't fit. It's like a lame version of Google Reader, without the awesome third party iPad apps.

In the interests of getting feedback from people that might not visit to leave comments, I'll be following this post in Google Buzz too, though it's probably the only thing in Buzz I will be following!

Like every man and his dog, I've been playing around with Google Buzz the last few days. So far it's looking quite good. It's not entirely accurate to call it a Twitter clone, but it certainly works in a very similar way.

If you'd like to have your blog posts (or other external content) posted on Twitter, you'd need to find a service that uses the Twitter API to post messages. Google Buzz works the opposite way, and Google will pull updates from other services (Twitter, Flickr, Blogs, Youtube, Google Chat, Picasa, Google Reader) and show them in your Buzz feed.

Currently, there's no built-in way to send your Buzz updates back to these services, though there are a few 3rd party services and workarounds to make this work.

DeWitt Clinton posted an interesting Buzz (?) about where Google Buzz is heading. It focuses on being open and interoperable. Rather than a closed system like Twitter, where you can only share with other Twitter users, Google are promoting an open system where different hosts can exchange messages with each other, like how other systems like Email and Google Wave work.

I have high hopes for Google Buzz. For too long have we put up with Twitter's fail whale and erratic API. It's time for their monopoly to end and everyone to play nicely together.

If you're giving Google Buzz a try, you can follow me using the button in the right column of my Google Profile page. If not, you can still find my ramblings on Twitter.