> > > > > The way the transport works is like a client on the jabber server. This client logs into the msn server and what it gets back from there it sends throught the wire to the real client (your computer).

> > > > Why not simply move that 'client' to the system of the user?

> > that would make you a server.

> I'm sure it could be modified to only allow local connections or to integrate it directly into jabber.

On linux, you have several instant messaging programs being developed that support multiple accounts and multiple protocols (jabber, ICQ, Yahoo!, MSN, AOL), all brought together into one integrated gui. Nice if you have more than one account. Don't know about Windows.

> > posible, but then If AOL/ICQ found out ther'd block your IP address.

> Really?
> Is it that easy to find out it's not a real ICQ client?
> Then why are non-real ICQ clients still being used?

AOL is more unfriendly than ICQ (also owned by AOL), and yes they do periodically search out people not using their client and then blocking them. Supposedly these third-party apps make the network unstable. Yeah right, they just want to lock-in your desktop :mad:


> > > I have one connection at work behind an HTTP firewall. quite common in work environments.

Unfortunately, this won't prove an easy way around this dilema.

We could all go off programming Jabber bits and pieces, but do we have the time? No. :(