Archive for January 7th, 2008

Which Nokia device to get?

I’ve developed a very strong desire to be connected to people recently. In the last fortnight I’ve reawakened my Google account and regularly sit on Google Talk, reawakened an old Free World Dialup account and plugged it into my home phone system, and signed up to Twitter. I also found a mobile IM and SIP client called fring that looks good and works really nicely. I’d love to use fring constantly, thanks to its integration to Twitter and Google Talk (heck, it might even make me find my old Skype ID) but…

My current phone is a Nokia N70, which has served me well for a couple of years, but I’m not keen to use it too much for fring because I don’t have a mobile data plan (and my phone company charges fairly steeply for casual data). Besides, it’s only UMTS 3G so the data rate is not great (better than GSM data, but only occasionally so). What I really need is one of the newer devices around that has Wi-Fi built in. Something like the N80, new N82 or E51, or N95. That way I could use fring at home (which is where I am most of the time nowadays) and not have to worry about data costs.

Thinking about spending that kind of money though (again, my phone company is happy to talk to me about upgrading my handset, but the kind of plan I’d have to go onto to get a phone like that would be insane) makes me wonder about other devices. Something like the N800, or even a new N810. I don’t think fring is available on Nokia’s tablet devices, but with the alternate OS platform on the N8x0 I could install just about any kind of IM client I want. Plus I’d have a nice device to web-surf, program MythTV, check mail, and various other tasks.

What about other devices? The Asus EeePC has tweaked my curiosity, but I think it would end up being just a bit too large to fit in with the kind of usage I’m imagining for this type of device. Blackberry is a bit scary to me, it doesn’t really seem to be a general-usage consumer-oriented device (more a corporate connect-back-to-the-proprietary-box-in-the-server-room kind-of thing). The iPod touch is out as well: it’s closed nature would frustrate the heck out of me (it’s got a browser, but you can’t load anything on it…). The only other manufacturer I’d think about for a mobile device right now is Sony-Ericsson: Ericsson manufactured a couple of the nicest phones I’ve ever owned, but Sony has ruined them for me. I’m just not interested in getting back onto the hardware-to-lock-users-to-the-Sony-tower treadmill.

It’s all just navel-gazing, unfortunately. Realistically, I can’t justify dropping a wad of money on some new shiny just to satisfy what is probably just a bit of a personal fad. I think I’ll wait a bit longer and see how quickly the newly-released N95-8GB drops in price, or how far it pushes the price of the old N95 down — ditto the N810 and N800.

Oh, and I’ll wait for fring to fix my biggest issue: no support for Jabber. Queries on their forum on this have gone unanswered for almost a year. Technically it can’t be a big leap for them, as they have support for Google Talk!

Tags: , ,

Jabber and Google, part one

I reactivated an idle Google account the other day. A friend of mine from the Netherlands invited me ages ago but I never really did anything with it until I discovered that a Google Mail account can be used for other Google stuff as well, including Google Talk. I read that Google Talk is based on Jabber and works with any Jabber client, so I flicked over to Kopete and plugged in the details. Sure enough it worked… but then it got interesting.

I run a Jabber server for internal things. I wanted to have a secure, private chat facility to use over VPN with my nephews; I want to someday migrate my Nagios IRC bot to Jabber; and I use transports to link into MSN and Yahoo! to reach friends on those networks. The last point is great: I really like the fact that now, from whatever Jabber client I use (even the mobile ones I’ve played with) that I merely connect to my Jabber server and I’m online on MSN and Yahoo! as well.

Google Talk, though, has proven to be a bit of a challenge. It’s actually working like a tower, even though it’s based on (arguably) the most open of the IM platforms! You see I more-or-less took for granted that “transport” way of doing things, using my Jabber server to bridge to other networks. There’s no Jabber transport for Jabber though!

What I want to do kind-of flies in the face of how Jabber is designed. Ideally, you’re supposed to only have one Jabber ID (JID) — Jabber creates an open network with servers establishing connections when needed, very much like e-mail, and you only need an ID on one server to be able to chat with anyone on any other server. So what I wanted to do, which was connect to one Jabber server and have it “relay” messages to an ID on a different server is just not necessary with Jabber. Nor should it be necessary for Google Talk users to send messages to me using my Google Talk ID only — they can send straight to my JID on my Jabber server.

In the early days of Google Talk, Google had not enabled the “server-to-server” functionality that allowed this kind of communication to happen. Google Talk worked just like MSN, Yahoo! or AIM — you had to have a Google Talk account to chat with anyone on Google Talk. While this was the case, folks were looking making a Jabber-Jabber transport for connecting Jabber servers to Google Talk. At some point, though, Google opened the connectivity paths that allowed Google Talk to exist on the open Jabber network (I’ve tested this for myself). Once this happened, the need for a  ”Google Talk Transport” for Jabber evaporated in most people’s minds.

The solution nowadays is to use a client that supports multiple connections, and connect to your Jabber and Google Talk accounts at the same time. It works of course, but you don’t get the nice benefits that a transport provides — the main one being access to all your IM services and accounts from a single server connection.

So now, having resigned myself to not being able to bring my home JID and Google Talk ID together, the question arose: do I still need my own Jabber server? My current fave mobile IM client only connects to Google Talk… Could I get by just using the Google Talk service? Find out in Part two! :)