comparison libfaim/README.gaim @ 302:61894ab8c47e

[gaim-migrate @ 312] I think logging in for oscar works a bit better now. committer: Tailor Script <tailor@pidgin.im>
author Eric Warmenhoven <eric@warmenhoven.org>
date Thu, 01 Jun 2000 10:06:37 +0000
parents 6e609d42f767
children 3069be4c291e
comparison
equal deleted inserted replaced
301:f905caee43ca 302:61894ab8c47e
81 fix for it, comment out the lines where it imports your buddy list in oscar.c, 81 fix for it, comment out the lines where it imports your buddy list in oscar.c,
82 and import it manually.) 82 and import it manually.)
83 83
84 - If you receive a message that's too large, gaim segfaults. I haven't watched 84 - If you receive a message that's too large, gaim segfaults. I haven't watched
85 this in gdb or gotten a backtrace on it, so I'm not exactly sure what the 85 this in gdb or gotten a backtrace on it, so I'm not exactly sure what the
86 problem is. 86 problem is. I think this actually happens on the TOC side of things too.
87 87
88 - Gaim/TOC can do file transfers, but Gaim/Faim cannot. This is not because 88 - Gaim/TOC can do file transfers, but Gaim/Faim cannot. This is not because
89 there is any difference in the two protocols as far as the actual transfer is 89 there is any difference in the two protocols as far as the actual transfer is
90 concerned. The only thing preventing this is it is currently not possible to 90 concerned. The only thing preventing this is it is currently not possible to
91 recognize when we've received a file transfer request using libfaim. Once 91 recognize when we've received a file transfer request using libfaim. Once