certificate

This is part 2 of a 2 part tutorial on Prosody, which will show you how to install and configure extra modules to extend prosody's functionality. Part 1, which deals with basic installation and testing of prosody, is here. Here's an overview of the important additional functionality we will add to prosody:

• Multi user chats (XEP-0045)
• Server side message storage (XEP-0313 Message Archive Management)
• File and image transfer (SI File Transfer and Jingle signalling; in-band and out-of-band methods)
• Stream Management for surviving connection interruptions and switches - particularly useful on mobile (XEP-0198 Stream Management)
• Synchronising messages between multiple devices (XEP-0280 Message Carbons)
• Battery Saving techniques for mobile clients (XEP-00352 Client State Indication)
• User Blocking (XEP-0191 Blocking Command)

Not all clients support all of these XEPs. I consider the Android client Conversations (F-Droid | Google Play) to be pretty cutting edge in this respect - it's pushing forward a lot of XEPs that are required if we are going to see XMPP compete with the features of proprietary chat clients, particularly on mobile.

At the end of 2013, I wrote a series of tutorials explaining how to run an email server at home on a raspberry pi, which turned out to be very popular. I'm now aiming to do the same for instant messaging. This tutorial will:

• Introduce the Extensible Messaging and Presence Protocol (XMPP), formerly known as "Jabber"
• Discuss some of the pros and cons of XMPP vs some other proprietary protocols
• Give instructions for the installation and configuration of Prosody, a free and open source XMPP server.
• Discuss various important XMPP Extension Protocols (XEPs) and how to enable them
• Cover transport layer encryption (i.e. client-server and server-server TLS) and end-to-end encryption for clients
• Recommend client software for different platforms

Along the way, I'll expose the underlying protocol to give you the tools you need to debug the problem yourself, instead of relying on obscured error messages from GUI applications. This is part 1 of a 2 part tutorial. Part 2 can be found here.