← All articles
Sovereign XMPP

Who knows you're typing — the small signals are yours too

19 November 2026 · 6 min · xmpp · typing-indicator · presence · xep-0085 · metadata · privacy · sovereign · self-hosting

We usually talk about owning a messenger in the language of the big things: keys, end-to-end encryption, who can read your messages, where your archive lives. Those are the pillars, and they’re real. But there’s a whole quieter floor of data that almost never makes the conversation, and it’s the one you’re broadcasting right now, even if you’re not sending a word.

You’re typing. Three dots sit at the top of somebody’s screen; somewhere, a small marker says your name is mid-sentence. You didn’t type a message yet — you typed a letter, or even just tapped the field — and already a fact about you is out in the world, moving between servers, deciding what someone else’s screen shows.

These are the small signals: that you’re typing, that you’re online, that you were here a minute ago. They’re ephemeral — they flare up and vanish — and because they vanish, we tend to think they don’t count. They count more than almost anything else. They’re metadata about a moment that is happening now, and on a rented messenger, every one of them is a little piece of your behavior that a vendor’s infrastructure gets to see, sort, and reuse.

The flimsy signals nobody prices

Think about what actually happens the second you open a rented messenger and begin to answer. The “typing…” indicator isn’t just a courtesy between you and your friend — it’s generated, routed, and logged by a chain you don’t control. The vendor’s servers see when you type, how often, who you type to, and how long the dots burn before you either send or give up. They see your presence: when you’re on, when you’re not, when you flicker on at 2 a.m. That is a behavioral fingerprint with a timestamp on every whisker.

None of it feels sensitive. That’s exactly the trap. We’ve been trained to protect the message but not the shadow the message throws. The big stuff is locked behind encryption; the small stuff — typing, presence, online status — often isn’t afforded the same care, because it’s considered too trivial to matter. Trivial to each of us, precious in aggregate: a record of precisely when you’re active, who you’re mid-conversation with, and how jittery your replies are.

On a server you own, the signals stay on your side

Here’s where sovereignty stops being a slogan about files and becomes something you can feel in the details. When your messenger runs on your own XMPP server, the ephemeral signals no longer detour through anyone else’s cloud to mean anything. Your presence state and your typing indicators travel over the same living, open protocol as your messages — and they route through the server you chose the same way your read receipts and your metadata do. There is no third party in the loop turning “your contact just typed” into a data point in their growth chart.

This is a fact of where the bits go, and it aligns the whole system the way it should: the person on the other end gets a truthful cue, and you are the one who decided what that cue is. You own the place where the signal is born.

A typing indicator that says what it is

The concrete version of that philosophy landed in the v0.9.102 release of Infium, on 3 November 2026. The release note is matter-of-fact:

“Typing indicator in the chat header: when someone is typing, you now see ’typing’ with animated dots next to their name at the top of the chat, just like Telegram.”

Behind that one-line note is a meaningful choice. The typing cue is built on XEP-0085 — the standard XMPP extension for chat-state notifications — and it sits in a carefully defined place: it replaces the status line at the top of the chat, and the same animated dots appear in your roster preview while a contact is composing. It’s an indicator of a state of the conversation, not a guessed animation pasted over an interface. It tells the truth because the protocol beneath it is honest, and the protocol is honest because it was made to be understood and run by anyone.

Why does that distinction matter for sovereignty? Because a “typing…” signal can be implemented two ways. One is a proprietary guesswork flourish inside a closed app — you can’t see what it’s doing, where it’s logged, or who it reports to. The other is a state a standard protocol emits from your client, through your own server, to a contact’s client, and you can inspect every hop of it if you want to. The difference isn’t the animation; it’s that one of them is yours and the other is opaque.

What you control is what the cue can’t fake

There’s a deeper symmetry here with something we wrote the other day about the right not to read. A rented messenger, hungry for engagement, was opening your last chat for you — forging a read mark in your name. It’s the same instinct, pointing the other way: a messenger decides facts about your attention and broadcasts them. In one case it fabricates that you read; with typing and presence it fabricates that you’re here, now, about to speak — and it does so because an active user is a valuable user.

A sovereign client has no reason to lie about you, and it has no engine pressuring it to. Your presence and typing state are emitted because you are genuinely present and typing, and they stop the moment you stop. There’s no engagement metric on your side of the server profiting from a phantom dot. The signal is only ever as meaningful as your actual attention — because the thing that produces it is yours.

The unglamorous heart of owning your data

Strip away the technical detail and you get the real definition of sovereignty, and it’s duller and more important than any single feature. Owning your messenger means you have decided, end to end, what happens to every fact about you that the tool produces — including the ones too small to have a name, that flare for a second and are gone. Not just the big encrypted words in the archive, but the flicker of “typing…” that told someone in another timezone you were still awake.

On your own XMPP server those small signals stay small and stay local. They cross the network over an open standard you can read, they route through a server you point to, and they say about you only what is true at that moment. That’s the quiet part of sovereignty, and it’s the part you feel every single day — because you’re typing something, somewhere, right now.

Infium is a live, end-to-end-encrypted XMPP server that treats the smallest signals with the same respect as the biggest messages. Request an invite or try the live demo — no signup wall, it runs in your browser.

← back to infium.net