|0x0002 ||Client ||Request rights information |
|0x0003 ||Server ||Rights information (returned after sending 0x0013/0x0003) |
|0x0004 ||Client ||Request aserver-stored information |
|0x0001 ||Server ||Error |
|0x0005 ||Client ||Request server-stored information |
|0x0006 ||Server ||Server-stored information (returned after sending 0x0013/0x0005) |
|0x0007 ||Client ||Activate server-stored information |
|0x0008 ||Client ||Add an item to the server-stored data |
|0x0009 ||Client ||Modify an item in the server-stored information |
|0x000a ||Client ||Delete an item from the server-stored information |
|0x000e ||Server ||Acknowledgement from add/modify/delete (0x0008/0x0009/0x000a) |
|0x000f ||Server ||Server-stored information unchanged (returned after sending 0x0005) |
|0x0011 ||Client ||About to modify list |
|0x0012 ||Client ||Finished modifying list |
|0x0014 ||Client ||Grant authorization to a contact without them asking for it |
|0x0018 ||Client ||Send ICQ authorization request |
|0x0019 ||Server ||Receive an ICQ authorization request |
|0x001a ||Client ||Accept or decline an ICQ authorization request |
|0x001b ||Server ||ICQ authorization request response (accepted or denied) |
|0x001c ||Server ||Contact added you to their list |
This family is used to handle various data which can be stored on the AIM servers.
Things that can be stored are your buddy list (with groups and buddy comments), your permit and
deny lists, your permit/deny setting, and your visibility setting.
The information is stored as "items." The structure is described here.
Buddy ID#s and group ID#s are arbitrary, though some clients tend to do it sequentially. They cannot, however, be 0x0000, and each ID# must be unique to the item that contains it (ie. two buddies in the same group can not have the same ID#, but two buddies in different groups can have the same ID#. Also, two groups in the list can not have the same ID#)(actually, we're
still not clear as an un-muddied lake on this)(it's possible that the ID#s are some kind of hash of the name).
For @mac.com screen names to show up in your buddy list, you must be using a family version of 3 or later (the most recent is currently 4). If you are using 1 or 2, AIM sends you your buddy list, but where you would normally have "email@example.com," they send "PleaseUpgrade000." The BID and GID are the same, and the list that's actually stored on the server still contains the firstname.lastname@example.org screen name--you just have to sign on with a client supporting a newer version of the SSI protocol.
Alex Yacoub had a big part in writing this, and helping figure out the protocol.
|0xffff ||N/A ||TLV Set - TLVs for additional data TLV chains for SSI items. |