XMPP service

Volatile XMPP federates with other XMPP servers, including those on Tor hidden services (needs testing). Efforts are made to support de facto modern XMPP standards (such as [XEPs]((https://xmpp.org/extensions/) and best federation practices (such as modern TLS ciphers).

OMEMO end-to-end encryption is strongly encouraged.

See this page for information on getting an account. Inline registration (straight from your XMPP client) is not possible.

Recommended clients

I use Conversations for Android. There are a few OMEMO-compatible desktop clients as well. Use what's best for you but be aware that an alarming number of clients are buggy or don't have full XMPP feature support.

For people who prefer a Web browser-based client, see the table below for links to the Converse.js webchat.

Server credentials

Technical details

• Daemon: Prosody
• Supported XEPs such as:
  • XEP-0045: Multi-User Chat, for conference rooms, available at muc.volatile.bz;
  • XEP-0191: Blocking Command, to block troublesome contacts;
  • XEP-0280: Message Carbons, allowing a user to see messages on all clients;
  • XEP-0313: Message Archive Management, allowing the server to store message history;
  • XEP-0352: Client State Indication, to reduce bandwidth, especially helpful for mobile connections;
  • XEP-0363: HTTP File Upload, an easier form of file upload;
  • XEP-0384: OMEMO Encryption, an end-to-end encryption protocol.
• IM Observatory TLS cipher reports:
  • Server-to-server
  • Client-to-server
• You get a username@volatile.bz address

Future considerations

• Add back xmpp.volatile.ano.
• Test Tor federation.
• Add DNS records for y.xmpp.volatile.bz.
• Consider warning on unencrypted chats (that is, any conversation between two people not using OMEMO, OTR, or PGP).