← All articles
Sovereign XMPP

Delivery you can watch, not guess

17 November 2026 · 5 min · xmpp · delivery · status · transparency · sovereign · self-hosting

You hit send, and then — nothing. The little circle spins, and you wait, because you have no real idea what’s happening to your words. Is it on its way? Stuck at a tower? Sitting on a vendor’s queue behind a billion other messages? The app gives you a spinner that means unknown, and the honest answer is that the renter knows exactly as much as you do — which is just about nothing.

That blind spot isn’t a small UX quirk. It’s the shape of the entire rental relationship: you hand your message to someone else’s black box, and from then on delivery is a matter of trust, not of checking.

The spinner that means “we’ll find out”

Think about what a sending animation actually tells you on a mainstream messenger. It tells you the request left your phone. It does not tell you where the message is, whether it’s still being processed, or whether it will ever arrive. The wheel spins either way — while the message flies, while it is genuinely stuck, or while it quietly fails. When something goes wrong, the most common outcome isn’t an error; it’s the message silently not arriving while the spinner pretends everything is fine.

There’s a sovereignty argument hiding in that opacity. Within a vendor’s cloud, delivery is a private internal process. You cannot inspect it, you cannot query it, and you cannot reason about it — you can only watch the animation and hope. The trust is one-directional: they promise, you wait.

Honest states, not a spinner

A messenger that treats you as the owner of the conversation shows you what is true, in small, verifiable steps — not a single ambiguous wheel. That’s exactly the direction Infium took most recently.

The anchor is v0.9.103 (2026-11-04). Its release note is a short sentence that carries the whole idea: “Messages now appear the moment you hit send. The bubble shows a small sweeping clock while it is on its way, then a check mark once it is delivered.” Not a spinner that means unknown — a trail: sent → on its way → delivered. You can watch the state change.

The same release note makes the point even more sharply in its cleanup: the old “Waiting for to update Infium” placeholder is gone, the note explains, “because outgoing messages simply show the sending clock until they are delivered.” No dead-end placeholder, no silent limbo — just an honest clock that keeps ticking until the message is truly delivered, at which point it becomes a check mark you can see.

Why it matters that you can see it

Opacity is comfortable for a vendor; honesty is what ownership looks like. When the status is visible, you are no longer praying into a pipe — you are watching a process you can understand, on a system that answers to you.

This is different from the guarantee we wrote about in delivery that survives your contact’s hardware. That piece is about the architecture deciding that the message gets there no matter what happened to the device. This one is about the visible side: that while it’s getting there, you’re told the truth at every step — not left to guess. Both matter, and they’re two halves of the same instinct: the messenger should do what it says, and show you that it did.

It fits the wider pattern of the release window. Around the same days, Infium also started showing the true read state instead of a flattering fiction — no fake “read” marks on messages you never opened, no silent “Seen.” in your name. Sending state, read state: the same philosophy applied to both directions of the arrow. A messenger you own doesn’t decorate reality, on the way out or on the way back.

On your own server, “delivered” is a fact you can check

The deepest difference is structural, not cosmetic. On a rented messenger, even a visible check mark is still something you have to take on faith — the state lives inside a proprietary backend you can’t inspect. On sovereign XMPP, your server is something you can point at. The delivery status is not a marketing graphic; it’s a state in the message’s lifecycle on infrastructure you control.

That’s what turns “delivered” from a claim into a fact. You don’t have to ask the vendor how the animation works — the mechanism is yours, open enough to trust, and honest enough that you don’t have to. The small decisions that decide whether a messenger feels like yours often come down to exactly this: a system that tells you the truth, on the level where you can check it.

The bottom line

The moment you hit send and see a wheel, you’re making a quiet deal: I trust the box, and I’ll find out how it went later. A messenger you own makes a different offer. It shows you the honest state of your message — on its way, delivered — and backs it with a server you can see. No black box, no guesswork, no silent swallowing.

That’s what sovereignty feels like at the moment your thumb leaves the screen. Not a mystery to hope about — a process you can watch, because it’s yours.

Infium is a live XMPP server with end-to-end encryption, built so the state of your messages is something you can see, not something you guess about. Request an invite or try the live demo — no signup wall, right in your browser.

← back to infium.net