Problem statement

User story: I am a privacy enthusiast who prefers OMEMO to Olm/Megolm. I want to log into an XMPP server, so that I can communicate securely with my friends who already use XMPP.

Suggested solution

• Deploy a Prosody server
• Ensure that a user with Librem One credentials can log in and communicate with someone on another XMPP server.
• Ensure that Chatty works as expected.
• The MUC domain will be conference.librem.one
• Branded apps are not required.

XEP requirements

These requirements are taken from Chatty 🎭 and Conversations 💬. Thus a Chatty user and a Conversations user should be able to chat in an OMEMO-encrypted MUC.

• XEP-0237: Roster Versioning 🎭 💬
• XEP-0198: Stream Management 🎭 💬
• XEP-0280: Message Carbons 🎭 💬
• XEP-0352: Client State Indication 🎭 💬
• XEP-0313: Message Archive Management 🎭 💬
• XEP-0363: HTTP File Upload 🎭 💬
• XEP-0065: SOCKS5 Bytestreams (or mod_proxy65) 💬
• XEP-0163: Personal Eventing Protocol for avatars and OMEMO 💬
• XEP-0191: Blocking command 💬

See https://modules.prosody.im/xeps.html for matching Prosody modules.

Notes

• OMEMO and Olm/Megolm are both double ratchet implementations.
• See also https://gultsch.de/omemo_by_default.html
• See https://compliance.conversations.im/server/conversations.im/ for compliance.
• See https://search.jabbercat.org/docs/operators for discoverability (low priority)