A friend of mine couldn't read my away message from centericq (based on
libicq2000), so I started debugging it to see what was wrong. I'm not
sure exactly when it stopped working, probably some time in October or
early November.
It turns out that libicq2000 doesn't want to check licq's away message
through the server because it doesn't think licq supports advanced
messages. From libicq2000-0.3.3/src/Capabilities.cpp:
bool Capabilities::get_accept_adv_msgs() const
{
return (has_capability_flag(ICQ) && has_capability_flag(ICQServerRelay));
}
Changing this method to always return true solves the problem, but I'm
suspecting that a more proper fix would be to make licq report that it
supports these two capabilities.
I tried looking into the capability-sending code in licq, but all I
could find was a bunch of undocumented magic numbers. In libicq2000
these two capabilities have the numbers 3 (ICQ) and 8 (ICQServerRelay)
if that means something to anyone. I don't even know if those numbers
have any meaning outside libicq2000.
So it it licq or libicq2000 that's broken here?
--
Jonas Jensen <[EMAIL PROTECTED]>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel
