Oscar Protocol Specification: Family 0x0004, Subtype 0x0014
unfinished
WinAIM5 and MacAIM support a sort of mini typing notification (MTN) that does not require a direct connection. Basically, when you begin typing something you send a "begin typing" message, then a few seconds later you send a "text has been typed" message, then after you actually send the message, you send a "no more text has been typed" message. You also send the "no more text has been typed" message if you delete all the stuff you've typed.
Remote clients know that your client supports MTN because the server appends an empty type 0x000b TLV to all outgoing IMs. You tell the server you want this TLV appended when you send the 0x0004/0x0002 SNAC. Flags should be 0x0000 000b.
Why the freak do the send and receive SNACs have the same family and subtype? I have no idea. My only explaination is that the oscar people are required to eat Amanita muscaria while on the job.
Thanks to Arun and Andrew for letting me use their computers :-)
Source: Client
| Length | Description |
|---|---|
| 2 bytes | Family (0x0004) |
| 2 bytes | Subtype (0x0014) |
| 2 bytes | Flags |
| 4 bytes | Snac Request ID |
| 8 bytes | Unknown (all 0s) |
| 2 bytes | Unknown (0x0001). I'm guessing this means this contains data pertaining to mini typing notification. |
| 1 byte | Length L of the follow |
| L bytes | The screen name of the person who sent this ICBM. |
| 2 bytes | The type of typing notification message.
|
All material Copyright © 2000-2014, All Rights Reserved
Linux is a registered trademark of Linus Torvalds.
AIM is a registered trademark of America Online, Inc.
ICQ is a registered trademark of ICQ Inc.
All other trademarks are property of their respective owners.