Email protocols history
A long time ago there was several protocols to send a message from a computer to an other one. There was a protocol per network (the internet was not really born at that time). Those protocols were not compatible between each others. So for instance, if you were using FidoNet, you were not able to send emails to people using BITNET. Hopefully some people created some gateways to transfer emails from a network to an other one (but it looks like it was quite a nightmare). At some point in time, ARPANET and its email protocol became the standard and other protocols started vanishing. People were now able to communicate with each other easily.
Instant messaging
Instant messaging (IM) appeared much more recently (email started in the late 60s, late 80s for IM). Personal IM became very well known in 1996 with ICQ (I still have my ICQ account! (but nobody to talk to me on it anymore)). Then several other protocols appeared:
Of course you can’t chat with somebody using MSN Messenger if you use Yahoo! Messenger. ICQ was bought by AOL, AOL created AIM (AOL Instant Messenger) based on ICQ protocol. At some point people using ICQ were able to speak with people using AIM.
In 2004, XMPP, the protocol used by Jabber, became the official IETF instant messaging standard (IETF is the group defining the internet standards (like HTTP for the web, SMTP for emails, FTP for file transfer
)).
Jabber/XMPP
XMPP as been the standard for 5 years now, but still, most of my contacts are using MSN Messenger. Why? Because they also use a Microsoft Windows based computer and Microsoft MSN Messenger is the default instant messaging software installed on those computers.
XMPP allows creating gateways to other protocols (like MSN, Yahoo!, ICQ
). The situation looks a bit like the email status in the old days. But the email standard imposed itself as the killer application of ARPANET. So, what will be the thing that will wipe out all proprietary protocols and impose the XMPP open standard?
The problem with standards is that it take time to be developed. History as shown that new versions of a standard are not implemented by all software vendors quickly, nor they are deployed as fast as possible. So changes to the standard must not happen everyday and having it quite right at version 1.0 take time.
In the meantime, other protocols evolve faster because vendors have a captive market and a better control on how the software is distributed/used (and they don’t have to wait for others to implement changes).
While XMPP was on the way to be standardized, other protocols got voice then video functionalities. I had a lot of hope in 1995 when Google released it’s own IM software Google Talk. GTalk is based on XMPP and add some voice extension and video extension later.
Then AOL started an experiment to allow XMPP connections to its network, Yahoo announced that they were interested by XMPP too. The chat in Facebook uses XMPP (but the network is closed, you can only talk to Facebook users), several other community websites do the same.
Nowadays
Last week, the specifications for voice/video in XMPP were released. The biggest missing features making people stay with their proprietary IM is going to be old story soon. But I’m not sure it will be enough to see a big migration to XMPP.
Those last few years, XMPP interest increased a lot and nearly all IM vendors are now looking at XMPP
except Microsoft. It looks like you will soon have the choice between speaking to nearly everybody except MSN Messenger users or speaking only to MSN Messenger users.
Of course there are lots of softwares allowing you to use several accounts at the same time (so being connected to MSN, Yahoo! and Jabber at the same time). I also have several emails account. The difference is that from my professional email account I can send emails to everybody, same for my personal email. I’m choosing the email account I’m using depending on what my “role” is. If I want to send a message to a colleague, I will use my professional email address.
In IM, you can’t do that, except if you open several accounts on each protocol you use. Having a professional and a personal account on MSN, on Yahoo!, on AIM, on Jabber
With all those protocols I currently have 9 accounts. And you know what? I like keeping things simple. For my email addresses I have started closing several accounts, keeping only the mandatory ones (my personal email address and the ones I have to use for my job). And I would really like doing the same for IM but you know what? Here I can’t do what I want. Why? Because if I close my MSN account, I will lose contact with a lot of people.
I feel a bit like in jail. Worse, I feel like my friends are in jail too but they are saying “Where do you see a jail? There’s only walls and fences”.
Anyway, lots of people are using GMail now, and there is a chat embedded in GMail. Of course this chat uses Google Talk so it uses XMPP. Even if I don’t really like GMail, I prefer having my friends using GMail/Google Talk than Hotmail/MSN Messenger (or whatever the name of those services are this week).
ejabberd
Since XMPP is an open protocol, anybody can implement it. There are several XMPP clients (Pidgin, Adium, Kopete, Trillian, iChat
) and there are also several servers.
In XMPP servers there is well-known one: ejabberd. This server is open source and written in Erlang. Ejabberd use the power of Erlang to be fault-tolerant, redundant, scalable, <add here any cool property a server should have>.
And since XMPP is a decentralized system, I can install my own server (as I did for my email server for instance).
Installing ejabberd on debian is as easy as usual:
$ sudo apt-get install ejabberd
To configure it, you just need to change the domain name to serve in /etc/ejabberd/ejabberd.cfg. If your domain name is example.org change the following:
%% Hostname {hosts, ["example.org"]}.
And set the admin user:
%% Admin user
{acl, admin, {user, "admin_user_name", "example.org"}}.
Add a user with the following command:
$ sudo ejabberdctl register user_name example.org password
Restart the server. Done.
Of course there are a lot more parameters to change if you want to fine tune it. You may also need to create a SRV entry in your DNS if your server is not the one serving “example.org” (but “im.example.org” for example).
. The bad news is that a lot of commercial products are using it (especially NAS devices like Drobo…).
). The script checks that the user executing it is the owner of… the script file! instead of checking that it’s the owner of the theme/plugin directory. Since they do the things right in debian, the script is owned by root but executed by www-data (apache’s user). So I had to change the owner of the script to make it work.
