Send zero byte file via sftp
* capability-info is a succession of capabilities LNTS cellular (if SMS-able string contains an ending ' SMS') WORD length of this record (you can't rely on fields if record isīYTE status (00 offline, 01 online, 02 not webaware) WORD affiliation/organization (0=disabled, other=see table) LNTS interests-specific (comma separated) WORD interests-category (0=disabled, other=see table) WORD past information category (0=disabled, other=see table) WORD country (0=disabled, other=see table) WORD protocol version (licq 0006, icq2000 0007, icq2001 0008)īYTE language (0=disabled, other=see table) IPADDR my ip address, often second NIC ip, leave 0 for noĭWORD port where listening for connections, leave 0 for no WORD status (sometime i saw bit 3 set, or bit 9 in invisible state)Ġ normally accepted (use this replying to auto-msg-req)Ĭ accepted to contact list (no blink in tray)Ġ4 00 = send to contact list (don't blink in tray) * status codes is a double word: WORD flags + WORD statusĢ000 direct connection only for contact listĠ002 show ip? (licq uses it on invisible state) * gmt offset is a signed byte, specifies negative half hours from GMT 0 * email-msg is a LNTS: name FE FE FE email FE unk-char FE body
* contacts-msg is a LNTS: contacts# FE uin FE nick FE uin FE nick FE. * user-msg is a LNTS: nick FE first FE last FE email FE unk-char FE msg * LNTS is a word (LE) preceeded NTS: the word indicates the length of theĪuto-msg-req (E8 away, E9 occupied, EA na, EB dnd, EC f4c)Ġ0 1D (probably) you're trying to reconnect too fast, wait a second String and the string report an uin number * B-UIN is a BYTE preceded STRING: the byte indicates the length of the * UIN is a 4-byte integer (LE) that codifies the uin number * STRING is a succession of (ascii) characters without length-leading or * COLOR is a quadruple of bytes: R,G,B,N where N is not used (you should * IPADDR is a quadruple of bytes A,B,C,D where in dotted form is A.B.C.D * where specified, communication is over SNAC protocol, over FLAP (AIM proto docs too) * communication is over FLAP protocol (find info about it in AIM protocol docs) * you won't understand too much in here if you don't read AIM protocol docs
* a list of people who contributed to this doc is at bottom * i don't earn money from this, i'm a student, i'm only having some fun.
* this doc is very bad written for several reasons i won't list here. If you want to tell me about additional info or wrong info in this file, contact me