XMPP Extension Protocols (XEPs) and Request for Comments (RFCs)
This page lists the supported XEPs and RFCs and informs about planned XEPs.
Kaidan supports the following XEPs:
|XEP-0004: Data Forms||v2.9|
|XEP-0030: Service Discovery||v2.2|
|XEP-0054: vcard-temp||v1.2||Only used for avatars and nicknames|
|XEP-0077: In-Band Registration||v2.4|
|XEP-0091: Legacy Delayed Delivery||v1.4||Read-only|
|XEP-0153: vCard-Based Avatars||v1.0|
|XEP-0184: Message Delivery Receipts||v1.2|
|XEP-0203: Delayed Delivery||v0.1|
|XEP-0231: Bits of Binary||v1.0|
|XEP-0280: Message Carbons||v0.8|
|XEP-0308: Last Message Correction||v1.0|
|XEP-0352: Client State Indication||v0.2|
|XEP-0363: HTTP File Upload||v0.9|
|XEP-0382: Spoiler messages||v0.2|
Supported XMPP Core RFCs
Kaidan supports the following RFCs:
- RFC-6120: Extensible Messaging and Presence Protocol (XMPP): Core
- RFC-6121: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
For file sharing we want to use XEP-0385: Stateless Inline Media Sharing (SIMS). This would allow us to also transmit a thumbnail (using Bits of Binary), the media type, the file size and checksums. SIMS is based on HTTP File Upload and can be implemented in a backwards-compatible way. SIMS also encourages developers to implement both HTTP File Upload and XEP-0234: Jingle File Transfer. But we are going to use only HTTP File Upload because it is already widely deployed and Jingle File Transfer has several downsides.
We decided to focus on implementing XEP-0369: Mediated Information eXchange (MIX) for group chats instead of XEP-0045: Multi-User Chat (MUC). There are already some experimental server implementations and as soon as there is a MUC <-> MIX mirroring, we will not have any disadvantages with it.
We are working on implementing XEP-0384: OMEMO Encryption with a user-friendly automatic trust management.