Note: See also https://github.com/otalk for more code
What is it?
While we have a version hosted at https://otalk.im, you can still run your own private instance.
git clone https://github.com/andyet/otalk.git cd otalk npm install node server
You can also run your own XMPP server.
Note: If you're running your own XMPP server, and aren't using something like HAProxy to terminate SSL, then you might get errors in certain browsers trying to establish a WebSocket connection because the XMPP server is requesting an optional client certificate which makes the browser terminate the socket. To resolve that, visit the XMPP over Websocket URL directly (eg, example.com:5281/xmpp-websocket for Prosody) so that a client cert choice can be made. After that, the Otalk client should connect fine.
Otalk comes with support for:
Message History Syncing
Using Message Archive Management (MAM, XEP-0313), your conversations can be archived by your server and pulled down by the Otalk client on demand.
Active Chat Syncing
Ever used multiple IM clients at once, or swapped clients, and end up with disjointed conversations? Using Message Carbons (XEP-0280) all of your active conversations will be synced to your Otalk client (and vice versa if you other clients support carbons too).
Sometimes you just lose your Internet connection, but with Stream Mangagement XEP-0198 your current session can be instantly resumed and caught up once you regain connection. Your messages will show as gray until they've been confirmed as received by your server.
Made a typo in a message? Using Message Correction XEP-0308 you can just double tap the up arrow to edit and send a corrected version. In other clients that support correction, your last message will be updated in place and marked as edited.
Working with someone in a different timezone? If the other person is using Otalk or another client that supports Entity Time (XEP-0202) you'll see a reminder that they're 9 hours away where it's 4am and they're not likely to respond.