|
AdHoc
End user PyICQt settings & commands
PyICQt supports different settings for every user. You can change them via Ad-Hoc menu (most jabber clients can do it) Statistics for PyICQt menuYou can see statistics for transport here
Set x-status menuYou can choose x-status and fill details for it using this menu Choosing is 2-steps process:
Settings menuThis menu contains several categories Contact list settings
When you delete contact from your ICQ contact list, it not deleted really, but marked as deleted and become 'temporary' contact. It's ICQ server feature to improve speed as I think (you may delete contact by mistake and restore it after some time - all this time contact is 'cached' in your contact list). Users wouldn't see these contacts usually, but it may be useful when contact-list on server is corrupted or user manually deletes all contacts from his own list and wants to restore them back. Number of temporary contacts is usually much more than number of real contacts (it is 141 vs 54 for me) and getting them from server can take a long time. If you enable this feature, you must re-login in PyICQt to apply changes. If you enable and disable this feature without re-login, PyICQt will not erase temporary contacts from your roster and you must delete them manually or re-register in PyICQt
Don't send subscription messages from ICQ contacts to jabber-client. This option useful for spam protection. All users requested authorization will receive 'Request denied' answer. X-status settings NOTE: administrator of PyICQt may disable x-status support for all users
NOTE: Icons for all activities (60+) aren't created yet, and it's impossible see icons for all x-statuses now.
Message settings
Send messages in utf-8 when: ...contact supports utf-8 messages (Always) ...contact really uses utf-8 (As reply on incoming utf-8 message) ...never (Sending disabled)
Send confirmations on incoming messages when: ...contact can receive them (Always) ...contact uses modern ICQ client (Only for utf-8 messages) ...never (Sending disabled)
Sends requests for messages confirmations. It's works when your jabber-client can send such requests (Bombus, for example) and contact's client can response on requests.
Send offline messages encoded in: ... local one-byte encoding, specified in config ... Unicode ... In depends on remote client features (auto detect) Personal events settings PyICQt tries to represent ICQ x-status for contacts as PEP event (you can read more about it at ExtendedStatus page) and uses for this aim 3 things: mood, activity and tune. Unfortunately, not all jabber-clients understand these things, and you can choose only some things, which are supported by your client. Most of clients supports moods and tune, support of activity isn't ready yet in most cases (seems only Gajim, Jabbim and Tkabber can display this in stable version, Miranda — only in unstable builds)
Clients supports personal events since versions:
NOTE: It's global settings for user. If you are connected to PyICQt with two and more resources, option apply for all them | ||||||||||||||||||||||||||||||||