The first faim block was worked around by changing some magic numbers in
the configuration struct that's sent to the server at login time. I have
no idea what most of this gunk is, and from the struct declarations it
seems that even the faim/gaim guys are in the dark about some of it :-)
Looks like TOT gaim is now making a pretty firm attempt to look exactly
like the Windows AIM client (down to the identical client name string.)
Those trying to keep their AIM transports up to date should keep polling
the gaim CVS repository at sourceforge.net. Look for recent checkins in
the oscar/ and faim/ subdirectories.
--Jens
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
