ICQ client firewall functionality also supports SOCKS.  Should the transport
try to do the same?

How should we handle memory problems? Of course, if one mallocs and assumes
it returns the proper memory, but it returns NULL, the moment one attempts
ot access kicks a Segmentation Fault. Do we want this? It seems rather safe,
but would we rather kick back with an error of why it happened. This would
require extra code and give the same information one could get with a
debugger. One more facet is that transports are often loaded under DSO, so
any segmentation fault would also bring down etherx. This should definately
be discussed on JDEV/#jabber.

Add a loopback ICQ call in the presence callbacks to automatically request
further away message information.

Support SIGHUP for reconfiguration.  The hook required is already in main.c.

Implement ICQ user info changing.  How would you set this via Jabber though?

Keep tracking new versions of the server.

