> > > > 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.

> 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?

> That means that it would block YOUR ICQ client. I would also leave you open for other people to invade your computer.

Unless it only allows local connections or you use a firewall.

> > > > > I have been thinking about writing a jabber client that was actually a proxy, but that would take time :(

> > > > a http proxy would be good. that way I could use jabber at school. I could go through the http only firewall. :) thats why I got ICQ in the first place. there is a prototype proxt being developed, http://www.jabbercentral.com and search the development section for transports IIRC.

> > > Is it really a HTTP firewall or is traffic simply restricted to port 80?

> The only way onto the net is through port 80 and ftp (21?).

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

> > pity they don't have a socks proxy.

> I don't think there is one. only the http proxy. spose it was chosen so people like me couldn't chew up bandwith with IM programs, etc. :)