rtyug

0 dev device number of filesystem
1 ino inode number
2 mode file mode (type and permissions)
3 nlink number of (hard) links to the file
4 uid numeric user ID of file's owner
5 gid numeric group ID of file's owner
6 rdev the device identifier (special files only)
7 size total size of file, in bytes
8 atime last access time in seconds since the epoch
9 mtime last modify time in seconds since the epoch
10 ctime inode change time in seconds since the epoch (*)
11 blksize preferred block size for file system I/O
12 blocks actual number of blocks allocated

METHODS

get_info (WHO)

Requests a user's information, which includes their profile and idle time. See the buddy_info callback for more information.
get_away (WHO)

Similar to get_info, except requests the user's away message instead of their profile.






send_typing_status (RECIPIENT, STATUS)

Send a typing status change to another user. Send these messages to implement typing status notification. Valid values for STATUS are:

* TYPINGSTATUS_STARTED: The user has started typing to the recipient. This indicates that typing is actively taking place.
* TYPINGSTATUS_TYPING: The user is typing to the recipient. This indicates that there is text in the message input area, but typing is not actively taking place at the moment.
* TYPINGSTATUS_FINISHED: The user has finished typing to the recipient. This should be sent when the user starts to compose a message, but then erases all of the text in the message input area.

evil (WHO[, ANONYMOUSLY])

Evils, or warns, a user. Evilling a user increases their evil level, which makes them look bad and decreases the rate at which they can send messages. Evil level gradually decreases over time. If the second parameter is non-zero, the evil will be done anonymously, which does not increase the user's evil level by as much as a standard evil.

You can't always evil someone. You can only do it when they do something like send you an instant message.
get_icon (SCREENNAME, MD5SUM)

Gets a user's buddy icon. See set_icon for details. To make sure this method isn't called excessively, please check the icon_checksum and icon_timestamp data, which are available via the buddy method (even for people not on the user's buddy list.) The MD5 checksum of a user's icon will be in the icon_md5sum key returned by buddy.

You should receive a buddy_icon_downloaded callback in response to this method.