Tomorrow’s News, Today: Google Talk

Share via Twitter Share via Facebook Share via Linkedin Share via Reddit

Screenshot of Google Talk on GAIM

Originally uploaded by sogrady.

As the /. crew has just discovered, Google’s new IM service Google Talk has gone live and reportedly will be announced tomorrow (er, today, now I guess). I’m not quite as excited as some of the commenters, simply because at the end of the day, it’s just another IM account – of which I have too many already.

The VOIP angle I suspect will get a lot of play, but a couple of the other services like Yahoo have had that for a while. There are, however, a couple of things worth nothing:

  • Jabber: Google gets a big thumbs up from me for refusing the temptation to create its own IM protocol, adhering instead to the prexisting Jabber open XML specification. Let’s hear it for open standards.
  • Cross-Platform: One of the biggest advantages to going with Jabber is that Google gets cross-platform support without lifting a finger. I’m currently running it on the GAIM client (which itself supports Linux, Windows and Mac), and Google’s got several other clients available – with configuration instructions. The VOIP feature is Windows only, and you don’t get the snazzy Gmail integration pictured on the Windows client, but at the very least I’ll be able to chat with my friends and coworkers that are on Gmail. Which brings me to…
  • Market: I haven’t seen subscriber figures for the various IM clients & protocols in ages, nor do I have any idea how many Gmail users Google’s allowed through the gates, but I do know a bunch of people who are candidates for this. A large contingent of my friends (and from conversations I’ve had with service providers recently, a large contingent of other peoples’ friends) have departed the likes of Hotmail and Yahoo Mail for IM. Strange as this may seem to kids, teenagers and people in technical professions, many of them still don’t use IM. Whether or not their pretty much unanimously positive experiences with Gmail will get them over the adoption hurdle remains to be seen, but I can pretty much guarantee that at least a couple of my friends will become immediate users.

Apart from all that, though, this is just the launch of an IM service. Is it important when seen in conjunction with the recent iteration of the Google Desktop package as another decided step towards the desktop? Undoubtedly. But the fact is that it’s after midnight now, and I can deal with that later 😉 Meantime, let me know how the Windows client is – I’ll give it a whirl myself tomorrow. Oh yes, my Google Talk ID is sogrady if you’re looking for someone to test it with. And if you haven’t managed to snag a Gmail invite yet, email me at my redmonk address – sogrady at redmonk.com – and I’ll hook you up with one of those.


  1. What parameters do you use for connecting for Gaim? Looks like your using jabber protocol, your gmail account without the @gmail, and gmail.com as the server. I can’t get those to work. I also tried talk.google.com as the server (since that’s what gmail talk is connecting – I used TCPView) which still doesn’t work for me in Gaim.

  2. hmmm…dunno what the problem could be. i couldn’t connect initally as i’d just done the username/pwd bit, but once i plugged in the talk.google.com bit i was fine.

    from the page here (http://www.google.com/support/talk/bin/answer.py?answer=24073), have you set the following up?

    # Jabber Options: Check the box next to ‘Use TLS if available,’ and leave the other boxes unchecked.
    # Port: 5222
    # Connect server: talk.google.com
    # Proxy type: Use Global Proxy Settings

    if so, i’m not sure what the problem might be.

  3. Seems there’s no Jabber networking supported – only users on @gmail.com can be reached. It would have been really interesting if there had been, but as it is it’s just another attempt to capture eyeballs…

  4. looks like they have plans to address your complaint, Simon:

    will be fun to watch.

Leave a Reply

Your email address will not be published. Required fields are marked *