On Sat, 14 Aug 2004 17:40:21 +0200 (CEST)
Martin Herzog <[EMAIL PROTECTED]> wrote:

Hello

> While analyzing the differences between the login procedures of licq and sim
> (which doesn't have this problem) I found that latter one sends a SNAC 13,7
> message. Including this in licq fixed the problem for me.
Thanks, I think this reasonable solution. As I can see in unnoficial (but almost
complete) specification of Oscar protocol SNAC 13,7 used as last packet in part of 
login sequence related to servers side contact list
(http://iserverd1.khstu.ru/oscar/login.html). And seems like many icq clients
used it this way.
So I think Licq also should use this request in the end of operations with
server side contact list at login stage.
I have made my own version of patch that add support of SNAC 13,7 to licq and attach 
it to this letter. One differences are that SNAC 13,7 sent not only
after SNAC 13,F (when contact list up to date), but also after SNAC 13,6 (when 
procedure of synchronization was prefomed). Second difference I tnink that separate 
class don't needed for this small control packet without payload.

But there are also bad news. This is sems fair but not complete solution.
With this patch I've get in online list some of users from my contact list, but 
approximately only 1/4 from group of users who are really online. I completelly 
synchronize my contact list with server but this didn't take effect. Also I used Sim 
and get the same result. Only 1/4 users online from that who must be online.
And most of users, who don't appear in online list grant me authorization, and i 
haven't any problem to add their to my contact list.
Before testing this patch I thought that AOL slighty change protocol and permit to add 
contact to buddy list only if contact permitted for adding to server side
contact list (i.e. have authorization). Proably this way AOL admins trying to fight 
with spam bots.
But now I think that was a wrong suggestion. Because I've registered new UIN, copy 
directory users and users.conf from directory of my main UIN to config directory of 
new UIN and start licq _without_ server side contact list support.
And all users who must be online scuccessfuly appeared on online list, and there is no 
any "Unknown Buddy Family Subtype: 0001".
So this problem related not only on client and protocol realization but also on UIN. 
I've read meny rumors on forums about what happened with this 'unlucky' UINs. One 
thinks that this is data corruption on main AOL servers (there is rumors that some 
people connected to backup icq servers with some tricks and there wasn't this 
problem). Also there is slighty paranoid suggestions that couple days ago AOL scan all 
connected clients and ban this way users who use not-native icq clients. I don't know 
what of this opinions closer to truth but still think that this problem can't be 
resolved only on client side.

SergK.

Attachment: list-activate.patch
Description: Binary data

Reply via email to