comparison libfaim/README.gaim @ 288:6e609d42f767

[gaim-migrate @ 298] Hopefully signing on will work a little better now. At least I know what's causing it. committer: Tailor Script <tailor@pidgin.im>
author Eric Warmenhoven <eric@warmenhoven.org>
date Wed, 31 May 2000 19:58:36 +0000
parents 0f14e6d8a51b
children 61894ab8c47e
comparison
equal deleted inserted replaced
287:8bbc269d5b8d 288:6e609d42f767
75 75
76 - "Allow anyone" and "Deny some" serve the same function. That's not a bug. But 76 - "Allow anyone" and "Deny some" serve the same function. That's not a bug. But
77 "Allow anyone" works all the time (?) and "Deny some" doesn't work some of the 77 "Allow anyone" works all the time (?) and "Deny some" doesn't work some of the
78 time. That's a bug. 78 time. That's a bug.
79 79
80 - Sometimes signing on doesn't work completely correctly. (If you want a bad
81 fix for it, comment out the lines where it imports your buddy list in oscar.c,
82 and import it manually.)
83
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
86 problem is.
87
80 - 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
81 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
82 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
83 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
84 libfaim can tell us that we've received the request, the only thing we should 92 libfaim can tell us that we've received the request, the only thing we should