powered by Jive Software

Looking Through The Fiery Gate

As many of you may have noticed. the IM Gateway plugin version 1.0 was released alongside Wildfire 3.2.3. (sorry guys, I can’t call it Openfire until the official release is 3.3.0 ) The release was quite a step for me as I’ve never actually released a 1.0 of anything! Typically I’ll take the attitude of having to get everything perfect before I can release a 1.0. One of the things that Jive helped me realize is that I could label some of the problem children (Yahoo, ICQ) support as experimental and basically release a 1.0 with good solid support for the rest of the protocols. That hadn’t occured to me before and I’m quite glad to see 1.0 out. Amazingly enough, there haven’t been a lot of bug reports. I hope that everyone who is using it is enjoying it.

I must admit that pushing Yahoo and ICQ support to the side “hurt” a little. However the library I’m using for Yahoo isn’t particularly stable and the ICQ support in joscar isn’t entirely golden either, and I didn’t want to see the release drawn out way into the future. I am pleased to say that the Yahoo library is getting some love as we speak and there’s been improvements to the ICQ support submitted to the joscar team and I’m working on a couple of other improvements. I would consider myself highly familiar with the OSCAR (AIM and ICQ) protocol itself, but not at all for Yahoo. (I’m referring to the low level details of how the protocol itself works, in theory the libraries I use ought to hide the details from me) As it turns out, I’m getting more familiar with the MSN protocol as I ended up taking over as lead developer of Java-JML. Thankfully, I’ve got some help on that front as well. It’s always nice to see help coming in from many angles!

So what’s coming next? Well, my highest priority is to get ICQ fixed up. Once the Yahoo library improvements come about, I’ll be aiming to solidify that as well. Of overall new features, I’m waffling between groupchat and file transfer. Groupchat is now the most voted for feature for the plugin. File transfer, on the other hand, is something I’ve never had an opportunity to get involved in, so generally I’m interested in learning how it works by diving into it. Buddy icons are also highly voted for. Such a seemingly pointless/unimportant feature, but I’m with you all; it’s one of the features that gives me the biggest joy to see in a chat client. They’re just so cute. ;D

Why did I title this Looking Throught The Fiery Gate? Well… it’s a gateway plugin… it’s in Openfire/Wildfire… yeah.

Just wanted to add my congrats on the 1.0 gateway plugin release. The gateways are amazingly easy to use as both a client and admin – definitely something never before seen in the XMPP world. I’m biased of course, but the gateway stuff rocks.

Thanks for all your work. The gateway plugin is really a great benefit for Wildfire/Openfire b.t.w. i am using icq in a productive enviroment since the very first day and never experienced any issues

keep up the good work and thank you!

I have to say I’m very pleased with the Gateway plugin. I can’t wait for the next release ^^.

Thanks for the good work.

I’ll have to second what other people have said, awesome job Daniel!

Without the work you’re doing, our IM support would have been much more difficult to implement.


Excellent job. Easy to use, and just what i need!

For future versions of the IM Plugin it would be a good thing to support invisible mode, as it would make it easier to convince friends to move to jabber. if they want to contact you, but don’t see you as online they probably have one more reason to get a jabber/xmpp account

That is, unfortunately, easier said than done. Thing is, if you set yourself invisible in XMPP, you are also setting yourself invisible to the transports themselves. Likewise, when I added a transport to my ‘visible’ list, there was nothing to indicate that I was really invisible. The people in your ‘visible’ list end up getting a normal available/whatever presence packet. =(