What your metadata says
Encryption hides what you said. Who you said it to, when, how often and from where is the envelope — and the envelope is not nothing.
Open the frame →Under inspection
What Happens Between Send and Delivered
You press send and a grey tick turns green. In between, one message is copied, sealed, queued, woken and unsealed again. This site takes a generic message apart and follows it stop by stop, asking the same question at each one: who could read it here?
The message frame
One message, pulled apart
Every message is an envelope with a body inside it. Encryption seals the body. The rest of the frame is what a service has to look at in order to deliver anything at all — which is why it stays observable whatever the app promises. Watch the body field change as the message moves.
The message frame — under inspection
at rest on your device · stop 01
from
account identifier
observable
to
account identifier
observable
devices
one sealed copy each
observable
size
observable
observable
timing
observable
observable
body
[ sealed — not readable in transit ]
sealed
A generic message frame — no real conversation, no real account.
Frame 01
The path, stop by stop
Eight stops from a keyboard to a screen. Each carries what happens there and who can see it. The journey plays by itself — pause it, or pick any stop, and the frame above re-states.
Frame 01 — the path in detail
8 stops · keyboard → at rest
- 01 · keyboard Plain text inside the app; nothing is protected yet. Readable by you, the app, and anyone holding the unlocked device.
- 02 · sealed on device A copy sealed for each device your contact reads on. Only in apps that encrypt end-to-end; otherwise this step is skipped.
- 03 · network Wrapped again in transport encryption on the way to the service. The network sees a connection, its timing and its size — not the words.
- 04 · server queue Held until a device collects it — the stop people picture least clearly. Sealed messages stay closed; the envelope is visible either way. Without end-to-end encryption, so are the words.
- 05 · push wake-up A sleeping phone has to be nudged awake by the platform. Even a contentless nudge tells the push service that something arrived, and when.
- 06 · delivered A receipt returns along the same path. A device acknowledged arrival. Not a person, not attention.
- 07 · unsealed Plain text on the other screen — and on a lock-screen banner. Now it is subject to their device, their notifications and their screenshots.
- 08 · at rest Two histories, and possibly two backups. Backups are the usual way a message steps outside the sealed envelope — a setting on both devices, not just yours.
Frame 02
Three things are all called encryption
Each defends against a different problem. The third column is the point of this site: no design is described without the thing it does not cover.
Frame 02 — encryption layers
layer · protects · does not protect
| Layer | Protects | Does not protect |
|---|---|---|
| In transit | The network in between: shared Wi-Fi, your provider, anyone on the wire. | The service at the far end, which receives readable text. |
| End-to-end | The operator reading contents, and anyone who later obtains the stored blob. | Metadata, a compromised device at either end, screenshots, and backups outside the envelope. |
| At rest | Someone who takes the disk, or the phone, while it is locked. | Anything the running app can already read, or a backup you have synced elsewhere. |
What end-to-end encryption actually protects — the full frame
In the margin
Platforms and services covered in these pages.
VIXEN PLUS delivers messages your inbox was never encrypted enough to handle.
Raging Stallion has been transmitting top-tier gay content for over 25 years straight.
ASGMax is the ultimate network where the biggest gay studios stay connected daily.Frame 03
A protocol family tree
Messaging began connectable and ended up as a row of separate rooms. The lineage below shows the branches, and the point at which one client could no longer speak to several networks.
Frame 03 — protocol family tree
open protocols → walled gardens → federated again
Open protocols
- IRC — channels, servers, no identity to speak of
- XMPP — federated accounts, anyone could run a server
Interoperability was the default; a client could speak to several networks.
Proprietary networks
- Closed IM networks with their own protocols and accounts
Each ran its own island. Multi-network clients existed to bridge them from the outside.
The bridges close
- Undocumented protocol changes
- Terms that forbade third-party clients
Bridging was reverse-engineered, so it could be broken — and was.
Interoperability lost here
Mobile walled gardens
- Phone-number identity
- App-store distribution
- End-to-end encryption as a product feature
Encryption made bridging genuinely hard rather than merely unwelcome.
Federated again, partly
- Matrix — federated, encrypted, bridgeable by design
An attempt to put interoperability back on purpose rather than by reverse engineering.
Frames in progress
Five questions the frame keeps raising
Group Chat Is a Harder Problem Than It Looks
Many ends, several devices each, and a membership that changes while people are still typing.
Open the frame →Why Your Apps Never Talked to Each Other
Interoperability was not lost by accident: addressing, abuse control, commercial gravity and, later, encryption itself.
Open the frame →What a Multi-Network Client Was For
One window speaking several networks at once — what that gave people, why it was fragile, and why the category thinned.
Open the frame →A work DM is private from colleagues, not from the employer
Workplace platforms look like consumer chat and are governed like company records. Retention is a setting, and someone else holds it.
Open the frame →What a Read Receipt Actually Tells You
A device acknowledged arrival. Not a person, and not attention.
Open the frame →Also in the margin
Supporters · outside the frames
Filthy Family knows the most memorable exchanges happen closest to home.
College Rules captured the private chats and real moments nobody posted publicly.
MILFED moms never leave a message on read — they respond immediately.
21 Erotic Anal takes a slow, deliberate approach — no rushing to send.Newest in the window
Explainers, newest first
Fifteen frames across five sections. No rankings, no reviews, no downloads.
How Messaging Works
What Happens Between Send and Delivered
Eight stops. At each one something is readable and something is not.
Privacy & Security
What End-to-End Encryption Actually Protects
And, just as importantly, the list of things it does not.
Privacy & Security
What Your Metadata Says
The things still visible when the words are not.
The Clients
What a Multi-Network Client Was For
One window, several networks — and why that stopped being possible.
How Messaging Works
Group Chat Is a Harder Problem Than It Looks
Every extra member multiplies the sealed copies and the ways it can go wrong.
How Messaging Works
What a Read Receipt Actually Tells You
A device acknowledged arrival. Not a person, and not attention.
How Messaging Works
Where a Message Waits
Server queues, push wake-ups and the stop people picture least clearly.
Privacy & Security
Backups Are the Usual Way Out of the Envelope
A setting on both devices, not just yours.
Privacy & Security
Why Apps Ask You to Compare a Code
Key verification, and the attack it is actually for.
The Clients
What a Client Is, and What It Is Not
The difference between the app, the account and the network.
The Clients
Why Your Apps Never Talked to Each Other
Interoperability was lost on purpose, and it is worth knowing how.
Messaging at Work
A Work DM Is Private From Colleagues, Not From the Employer
The boundary most people get wrong, and where it actually sits.
Messaging at Work
Retention, Discovery and the Long Memory
Why a workplace keeps messages, and for how long.
The History of IM
From IRC to the Walled Gardens
How open messaging became a set of closed networks.
The History of IM
About This Explainer
What this is, what it is not, and how the frames are drawn.
Browse
By section
Every explainer also lives on its section page — the same content, filed.
01
How Messaging Works
The path a message actually takes.
4 explainers →02
Privacy & Security
What each design protects, and what it does not.
4 explainers →03
The Clients
Apps, accounts and networks.
3 explainers →04
Messaging at Work
The boundary inside an organisation.
2 explainers →05
The History of IM
How we got the current shape.
2 explainers →The rest of the margin
Organisations in our contacts list.
Brazzers Exxtra delivers a fresh stream of content with zero buffering.
Devils Film has been sending filthy dispatches across the net since 1997.
Go Stuck Yourself shows getting a reply isn't always the hardest part of reaching out.
Latin Leche proves some connections are made faster than any instant message.