What It Means That Dino Is Built on XMPP and Is Decentralized

Updated

Dino is a desktop chat client built on XMPP, an open internet standard for instant messaging. "Decentralized" means Dino doesn't route your messages through one company's servers: you pick (or run) an XMPP server, and that server can talk to any other XMPP server worldwide — the same way email works across providers. This matters if you want to choose your own provider, avoid a single point of control, or even host your own server.

XMPP: the protocol underneath Dino

XMPP (Extensible Messaging and Presence Protocol) is an open standard for communication, mainly used for instant messaging. Per Dino's site, it is a secure, battle-tested protocol developed by an independent standards organization. The "X" stands for "Extensible," meaning the protocol can be extended with new features rather than being frozen by one vendor.

Dino itself is just the client — the app you install on your desktop. It speaks XMPP to a server, and that server handles delivery to your contacts.

What "decentralized" actually means here

Dino's site describes XMPP as "the instant messaging pendant to email." That analogy is the clearest way to understand decentralization:

  • No single provider required. You don't have to rely on one provider or company. Instead, you use a federated, world-wide infrastructure.
  • Federation. Your server and your contact's server exchange messages with each other, even if they're run by different people or organizations.
  • Self-hosting is possible. You can even host your own server, according to Dino's site.

So "decentralized" is not a feature you toggle in Dino — it's a property of the network Dino plugs into. Dino is the client; XMPP is the network.

Email as the mental model

Email XMPP with Dino
You have an address at some provider You have a Jabber/XMPP address at some server
Providers deliver mail to each other Servers federate messages to each other
You can run your own mail server You can run your own XMPP server
The client (e.g., a mail app) is separate from the server Dino is the client; the server is separate

Why this design matters for privacy and control

Dino's site frames decentralization alongside two other principles:

  • Encryption. Dino is secure by default: chats never leave your computer unencrypted. Once you enable end-to-end encryption via OMEMO or OpenPGP, only you and your chat partners can read your messages — not your server administrator or anyone else. You can also disable read and typing notifications globally or per contact.
  • Free Software. Dino is free and open-source, developed on GitHub by an open community. Anyone can inspect or modify it, so you don't have to trust a single company or development team.

Decentralization complements these: because you aren't locked to one operator, you have more say over where your data lives — and end-to-end encryption means the server operator can't read your messages anyway.

What this means in practice

If you're deciding whether Dino fits your situation, the practical implications are:

  • You need an XMPP account on some server. Dino is a client, not a service. Your account lives on a server you choose or run.
  • You can talk to people on other servers. Federation means your contacts don't need to use the same provider as you.
  • You can change providers without changing clients. The client and the server are separate layers.
  • You can self-host if you want full control. Dino's site explicitly notes this option.

If instead you want a single company to manage everything for you, a centralized chat service will feel simpler — that's the trade-off decentralization makes.