[JDEV] Jabber Transports - New Architecture

[Peter Saint-Andre]

On 7 Mar 2002, Julian Missig wrote:

> The transports were created to ease the transition to Jabber.

This to me is the most interesting point. What *else* can we do to ease
the transition? Given the recent changes by Yahoo and the fact that MSN
could change its protocol tomorrow on a whim (I won't even mention AOL), I
feel it's becoming obvious that the only way Jabber will have any impact
in the IM world is to grow fast enough and big enough that other IM
systems have to sit up and take notice. So what do we need to do in order
to grow that fast and become that ubiquitous?

Here's a short list:

1. Killer clients for Windows and Mac (face it, not everyone runs Linux ;)

2. Easier server administration to penetrate more organizations and ISPs

3. Windows server (see points 1 and 2)

4. Even better security

5. Reliable file transfers

6. Other popular features (even emoticon images, much as I dislike 'em)

I know people want immediate gratification and interoperability now, but I
say screw the transports -- let's build a truly open IM network, not spend
our precious energy hacking up gateways to closed systems.

Peter

--
Peter Saint-Andre
email+jabber: stpeter at jabber.org
weblog: http://www.saint-andre.com/blog/