Bitlbee-discord is a plugin for Bitlbee which provides access to servers running the Discord protocol.

This package provides Ejabberd -- Robust, Ubiquitous and Massively Scalable Messaging Platform. It supports XMPP, MQTT and SIP protocols.

This module implements XEP-0363: it allows clients to upload files over HTTP.

Ytalk is a replacement for the BSD talk program. Its main advantage is the ability to communicate with any arbitrary number of users at once. It supports both talk protocols ("talk" and "ntalk") and can communicate with several different talk daemons at the same time.

This package shows CAPTCHA without running proprietary code.

This package provides account management tools for Discord.

Mcabber is a small XMPP (Jabber) console client, which includes features such as SASL and TLS support, Multi-User Chat (MUC) support, logging, command-completion, OpenPGP encryption, Off-the-Record Messaging (OTR) support, and more.

This module implements support for a Tigase XMPP extension, Priority of notifications. It is a custom extension to XEP-0357: Push Notifications.

Pidgin-OTR is a plugin that adds support for OTR to the Pidgin instant messaging client. OTR (Off-the-Record) Messaging allows you to have private conversations over instant messaging by providing: (1) Encryption: No one else can read your instant messages. (2) Authentication: You are assured the correspondent is who you think it is. (3) Deniability: The messages you send do not have digital signatures that are checkable by a third party. Anyone can forge messages after a conversation to make them look like they came from you. However, during a conversation, your correspondent is assured the messages he sees are authentic and unmodified. (4) Perfect forward secrecy: If you lose control of your private keys, no previous conversation is compromised.

MQTT and MQTT-SN are lightweight publish/subscribe messaging transports for TCP/IP and connection-less protocols (such as UDP). The Eclipse Paho project provides client side implementations of MQTT and MQTT-SN in a variety of programming languages. This package is for the Python implementation of an MQTT version client class.

Gajim aims to be an easy to use and fully-featured XMPP chat client. It is extensible via plugins, supports end-to-end encryption (OMEMO and OpenPGP) and available in 29 languages.

This package provides python-pypresence, a Discord RPC client written in Python.

pn provides a command line tool that allows users to operate on phone numbers (get validity information, reformat them, or extract numbers from a text snippet), using libphonenumber.

This package provides a fork of libsignal-protocol-c, used by Dino to provide OMEMO support.

mtxclient is a C++ library that implements client API for the Matrix protocol. It is built on to of Boost.Asio.

Purple-Mattermost is a plug-in for Purple, the instant messaging library used by Pidgin and Bitlbee, among others, to access Mattermost servers.

Profanity is a console based XMPP client written in C using ncurses and libmesode, inspired by Irssi.

senpai is an IRC client that works best with bouncers.

This library implements OMEMO of XMPP (XEP-0384) in C.

ngIRCd is a lightweight Internet Relay Chat (IRC) server for small or private networks. It is easy to configure, can cope with dynamic IP addresses, and supports IPv6, SSL-protected connections, as well as PAM for authentication.

Meanwhile is a library for connecting to a LIM (Lotus Instant Messaging, formerly Lotus Sametime, formerly VPBuddy) community. It uses a protocol based in part off of the IMPP draft(*1), and in part off of traces of TCP sessions from existing clients.

This module implements XEP-0198: when supported by both the client and server, it can allow clients to resume a disconnected session, and prevent message loss.

Pidgin is a modular instant messaging client that supports many popular chat protocols.

This module implements XEP-0357: Push Notifications.

Some platforms, notably Apple’s iOS and many versions of Android, impose limits that prevent applications from running or accessing the network in the background. This makes it difficult or impossible for an XMPP application to remain reliably connected to a server to receive messages.

In order for messaging and other apps to receive notifications, the OS vendors run proprietary servers that their OS maintains a permanent connection to in the background. Then they provide APIs to application developers that allow sending notifications to specific devices via those servers.

When you connect to your server with a client that requires push notifications, it will use this module to set up a “push registration”. When you receive a message but your device is not connected to the server, this module will generate a notification and send it to the push gateway operated by your application’s developers). Their gateway will then connect to your device’s OS vendor and ask them to forward the notification to your device. When your device receives the notification, it will display it or wake up the app so it can connect to XMPP and receive any pending messages.