What’s worse about it is that although jabber supports transports, I really doubt that anyone is going to bother to write a jabber-to-jabber transport to support Google Talk — because anyone who would be capable of authoring such a transport is likely to be incredibly peeved about the lack of proper s2s support [in the first place.]
It’s too true, ladies and gentlemen. While Google Talk may be based on Jabber, it’s sadly not quite there just yet. Until I can add my non-Googleised account to someone’s contact list and talk to them with it, I’m afraid it’s just not working for me.
In other news I’m setting up a little Debian workstation for in the lounge room. Carl thinks it’s a horrible idea (“What a waste of power, blah blah!”) although he has no legs from which to complain whilst standing. He needed to dry clothes the other day, so he stole my fan and turned it on full power alongside his own for the entire day, pointing at the washing rack. Could’ve just hung them up properly instead of just draping them around the place.
Responses
At The Techtoucian Network, we're a bunch of hippes, and love your conversation! Please keep it real though; check out comment policy to see what we're all about.
Post a comment or leave a Trackback.
3 Comments
if you think that google talk sucks, then your busyness certainly has some jealousy issues. google talk can do every thing that you said it couldn’t and I am offended because google talk works fine for me!!!
No offense was intended at all. At the time of writing, Google Talk was nothing but another closed IM network.
I haven’t used it recently, and none of my friends have either. I think they missed the interoperability boat completely, and now nobody’s really that interested.
I’ve used the gmail embedded google talk to talk to other jabber servers (specifically, volity.net). So that problem appears to have been fixed.
Thanks for your feedback.