Yesterday I ran across an extremely exciting fact: AOL is now running an XMPP server at xmpp.oscar.aol.com that accepts logins from AIM/ICQ accounts and can talk with AIM/ICQ contacts. This means that there's suddenly 53,000,000 more people (according to 2006 numbers from Neilsen/Netratings) that are accessible from XMPP. I've made a brief timeline of important events in XMPP's growth.

 

1999: Creation of XMPP

2003: Jive Software releases the first version of Jive Messenger

2003: XMPP passes ICQ in number of users

2004: IETF approves XMPP as an official standard

2004: Google Talk released, dramatically increasing XMPP's market reach

2005: Apple announces XMPP support in iChat and Mac OS X server

2006: LiveJournal adds XMPP support, creating 14 million XMPP accounts in the process

2008: AOL creates an XMPP-OSCAR bridging server, adding another 50 million or so users accessible via XMPP

 

As you can see, over the last four years XMPP has gone from a relatively tiny force to a huge player in the IM world. Now all we need is for Microsoft, Yahoo, and QQ to follow suit and most IM users will be able to talk to each other without the hassle of creating accounts on each service and using lots of different programs (or multi-protocol programs) to connect to them.

 

I'm extremely excited about the possibilities of this, although a little worried about the lack of public acknowledgement from AOL. Hopefully they will continue to move forward with this, and make an announcement in the near future.

3 Comments Permalink

One of the things you may have noticed that appeared in the 3.4.3 release of Openfire is a couple of new installers, and some improvements to existing installers.  Oddly enough, building installers can be one of the more difficult tasks a developer has.  Simply putting out a tarball or zip file is easy, but it's not exactly the most pleasant thing to deal with from an administrator perspective.  In the process of creating installers, you often find yourself fighting with differing standards between OS distributions, or different architectures altogether.  That said, typically once you have created the installer, there's not much to do with it after, so it's generally a one time cost, so to speak, and the benefits far outweigh the time spent!

 

In an effort to make Openfire as easy to install as possible, we added official Debian and Solaris packages.  Yes, I am aware the Solaris package is listed under Linux right now, but please ignore that for now.    Are we stopping there?  Not really.  I'm not yet sure what other OS's we might be providing packages for at this point.  FreeBSD is about the only other one I've seen a request for and there's a well maintained port (net-im/openfire) of Openfire already.

 

What we are investigating now is providing hosted repositories for the packages.  Specifically, I'm looking at a Yum and APT repository at the moment.  This would allow system administrators to point their repository configs at our repositories and be able to easily keep up to date.  We are still working out the logistics of this, so stay tuned!

 

We're also investigating getting Openfire into more distributions.  In other words, instead of having to come to our site to get Openfire, perhaps you could install it from a central Debian repository, or an extras cd, or something of that nature.  There are a couple of possibilities in the works on that front, and a couple more I'd like to pursue.

 

So hopefully in the near future, it will be as easy as ever to get rolling with Openfire!

18 Comments Permalink