Jabber protocol

From Miranda NG
Plugin:Jabber
Jump to navigation Jump to search
Jabber protocol
Jabber protocol
Filename Jabber.dll
Authors George Hazan, Maxim Mluhov, Victor Pavlychko, Artem Shpynov, Michael Stepura
Download links
Stable version: 32-bit, 64-bit
Development version: 32-bit, 64-bit

Jabber (XMPP) protocol support for Miranda NG.

Supported XEPs

Miranda NG currently supports the following XEPs:

Click here to toggle the list
Click here to toggle the list

Troubleshooting

  • Autojoin is not working when using OpenFire with Active Directory authorization Use server FQDN as server name in Miranda instead of domain FQDN.
HTTP File Upload
  • XEP-0184: Message Delivery Receipts works only when the Jabber client at the other end can respond with message acknowledgement. If your messages seem to time out all the time, try disabling this option.
  • To use XEP-0363: HTTP File Upload, enable Protocol menu → Services... → Service discovery → Right-click on service → Use for uploads option.
  • Stream compression can lead to problems when using OpenFire.
  • Spaces in login/password should be replaced with \20 when using OpenFire.
  • In order to obtain contact's resource (for passing to Actman) install Variables plugin and use the following code:
?puts(v,!dbsetting(%subject%,?cinfo(%subject%,protocol),display_uid))
?if(?greater(?strrchr(?get(v),/),0),?substr(?get(v),?add(?strrchr(?get(v),/),1)),)


Hidden settings

To add/change these options you will need Database Editor plugin.

Hidden settings per-account
Setting Type Default Description
ConnectionKeepAliveInterval Dword The interval (specified in milliseconds) beetween keep-alive pings.
Identity String Spoof client version to the specified value.
Hidden settings per-contact
Setting Type Default Description
DisableOmemo Byte 0 1 = Disable XEP-0384: OMEMO Encryption support for this contact.

GNU GPL special exception

As a special exception, the authors give permission to modify code, dynamically link and distribute the Program in binary form within the QIP installer or archive, as long as the following requirements are fullfilled:

  1. The Jabber plugin must be announced and advertised as a separate product, clearly stating that the Jabber protocol is supported via a separate plugin ported from Miranda.
  2. Any kind of QIP Infium distribution must include this license agreement and original copyrights.
  3. The original copyrights must be available within the UI.
  4. Each version of the modified code must be freely available.
  5. Any changes made in the source code are subject to this license.

See also

Auto-join group chats

Setting up SSO/AD with Openfire (GSSAPI)

Install ejabberd with Active Directory SSO backend

Connecting to the LoL chat using XMPP

Connecting to Hipchat using Miranda