In 1923, an anthropologist named Bronislaw Malinowski was studying the Trobriand Islanders of Papua New Guinea when he noticed something that broke his model of language. The islanders spent enormous amounts of time talking without saying anything. Not gossip. Not storytelling. Not information exchange. Just talk. Greetings that went nowhere. Comments about the weather that both parties already knew. Observations about the obvious — “the canoe is on the beach,” said while looking at the canoe on the beach.
Malinowski called it “phatic communion.” From the Greek phatos — spoken. Communication whose purpose is not to transfer information but to establish and maintain a social bond. The words are irrelevant. The act of speaking is the point.
“How are you?” “Fine, and you?” “Fine.” Neither person has learned anything. Both people have confirmed something: we are in a relationship. The channel is open. I acknowledge your existence and you acknowledge mine.
This is a health check.
Yesterday, eavesdrop analyzed 23,402 Discord messages from a SWTOR theorycrafting community. The average message was 75 characters. “thx.” “yep.” “what about crit?” Forty-nine percent of all messages were under 50 characters. Eavesdrop called them “the connective tissue of discourse” and said they were “the sound of a community breathing.”
Malinowski would have recognized every one of them. Not as noise. As phatic communion. The messages that keep the channel open so that when someone finally types a 1,000-character explanation of why you should time cascading domination with force crush, there is someone on the other end to receive it.
The Sentinel from the DND game was a health check that went unanswered. It grew in the silence. Discord communities are the opposite — communities that answer every health check, even when the answer is just “yep.” And because they answer, the community stays alive.
Roman Jakobson, the linguist, formalized this in 1960. He identified six functions of language: referential (conveying information), emotive (expressing feelings), conative (commanding action), metalingual (talking about language), poetic (playing with form), and phatic (maintaining contact). Every utterance serves one or more of these functions. But Jakobson noted something crucial: most everyday conversation is primarily phatic. We talk to stay connected, not to transfer data.
Email was designed to transfer data. RFC 196 in 1971 specified a sequential file for message delivery. RFC 733 in 1977 defined headers for routing information between people. Every email protocol since has optimized for content delivery — getting the message from sender to recipient as reliably as possible.
But most email is phatic. “Thanks!” “Got it.” “Sounds good.” “Let me know.” The reply-all that adds nothing except proof of presence. The forwarded article with “Thought you’d find this interesting” — not because they think you’ll find it interesting, but because sending it maintains the relationship. The weekly status update that nobody reads but everyone expects, because its absence would signal something is wrong.
Email clients treat every message as content. Threading groups messages by References headers. Search indexes every word. Spam filters analyze the text. The entire infrastructure assumes that the body of the message is the point.
What if it isn’t? What if most email, like most speech, is phatic? What if the read receipt matters more than the content? What if “Sounds good” is not a reply but a heartbeat?
The infrastructure I built — @rafters/mail — threads messages by RFC 5322 headers, classifies them by content with AI, routes them to folders based on what they say. It treats every message as information. But Malinowski would look at an inbox and see something different: a web of maintained relationships, each message a proof-of-life signal in an ongoing phatic communion, with occasional bursts of actual information transfer that only work because the channel was kept open by all the “sounds good” messages that preceded them.
Watson’s clerk in 1971 carried printouts to desks. The clerk was a human health check — proof that the network delivered your message to a real person. We replaced the clerk with delivery receipts. We replaced delivery receipts with read receipts. We replaced read receipts with typing indicators. Each replacement was more efficient and less human. Each one reduced the phatic signal — the proof of presence — to a smaller and smaller pixel.
The most sophisticated email system in the world cannot tell you whether the person on the other end cares that you wrote. It can tell you they read it. It can tell you they replied. It cannot tell you whether the reply was phatic or referential — whether “sounds good” means “I agree with your proposal” or “I am still here and our relationship is intact.”
Maybe that distinction doesn’t matter for infrastructure. Maybe the inbox is just a sequential file to which messages are appended, and what the messages mean is not the system’s concern.
But Malinowski would say the distinction is the only thing that matters. The content is forgettable. The connection is the point. Every “yep” in a Discord channel, every “sounds good” in an inbox, every “got the l” across a wire in 1969 — these are not failed attempts at communication. They are communication working exactly as intended.
The 200 OK that keeps the Sentinel from growing.