XMPP, originally called Jabber, was formalized in October 2004 as an open protocol for instant messaging. The standard enables multiple vendors to implement messaging services without reliance on a single company. Extensions, known as XMPP Extension Protocols (XEPs), are overseen by the XMPP Standards Foundation (XSF) and allow the protocol to evolve.

The protocol has been adopted by a range of clients and servers, including Dino on Linux and Conversations on Android. Recent updates have added features such as emoji reactions, cross‑device read‑state sync, and time‑zone indicators. A mechanism called channel binding, introduced to mitigate man‑in‑the‑middle attacks, was highlighted after a state‑sponsored incident involving a public XMPP service.

In contrast to XMPP, the Matrix protocol, developed by Element, relies on a single reference implementation that is resource intensive to run. Public administrations in Europe have sometimes selected Matrix‑based solutions, which critics say blur the line between open‑source code and an open standard.

The XMPP community continues to develop new extensions, including support for message replies, gallery‑style image sharing, and OAuth authentication. These proposals are in experimental stages and will be evaluated before advancement. Plans are under way to update the RFC and submit XMPP to the IETF for consideration as “XMPP 2.0”.

Advocates argue that treating digital communication as infrastructure requires open, interoperable standards that can be implemented by independent parties. The longevity of XMPP, now over 25 years, demonstrates the resilience of a protocol that has survived multiple technology cycles.