website/content/documentation/features.md

title	date	draft
Mercury Feature Support	2019-09-07T01:18:54+02:00	true

Mercury aims to be compliant to RFC 6120: Extensible Messaging and Presence Protocol (XMPP).

XEP Support

Mercury currently has explicit support for the following XEPs:

• XEP-0030: Service Discovery
• XEP-0060: PubSub
• XEP-0092: Software Version
• XEP-0115: Entity Capabilities
• XEP-0163: Personal Eventing Protocol
• XEP-0198: Stream Management
• XEP-0237: Roster Versioning
• XEP-0280: Message Carbons
• XEP-0352: Client State Indication
• XEP-0359: Stable and Unique Stanza IDs (see comments)
• XEP-0392: Consistent Color Generation

Planned XEP Support

The following XEPs are on the TODO list:

• XEP-0045: Multi User Chats
• XEP-0048: Bookmark Storage
• XEP-0054: vcard-temp
• XEP-0077: Inband Registration
• XEP-0080: User Location (see comments)
• XEP-0084: User Avatars (see comments)
• XEP-0085: Chat State Notifications
• XEP-0184: Message Delivery Receipts
• XEP-0192: Blocking Command
• XEP-0249: Direct MUC Invitations
• XEP-0308: Last Message Correction
• XEP-0313: Message Archive Management
• XEP-0363: HTTP File Upload
• XEP-0373, XEP-0374: OpenPGP for XMPP
• XEP-0384: OMEMO Encryption
• XEP-0394: Message Markup
• XEP-0410: MUC Self-Ping
• XEP-0420: Stanza Content Encryption

Refused XEP Support

The following XEPs are not currently on the TODO list:

• XEP-0071: XHTML-IM (see comments)
• XEP-0357: Push Notifications (see comments)

Comments

• XEP-0071: XEP is deprecated and considered a potential security risk
• XEP-0080: Presumably in form of an addon?
• XEP-0084: Work is currently done upstream in Smack
• XEP-0357: Mercury embraces decentralization and independence. This is not compatible with being functionally dependent on centralized push services.
• XEP-0359: Currently broken upstream, but a fix is submitted