A link arrives in the group chat with the message “THIS.” Clicking through reveals a four-thousand-word investigation into something politically charged, and within seconds we can tell that whoever sent the link never made it past the headline. What got shared was the headline’s implication, the outline of what the piece seemed to promise. The contents didn’t seem to have entered the equation.
That exchange violates a rule of information etiquette. Information etiquette is the interpersonal counterpart to information literacy: the layer of unwritten social norms governing how we handle information with each other, alongside the individual work of evaluating what’s true. Its rules are what we feel getting broken when a message lands wrong, invisible until somebody breaks one and unmistakable in the moment they do.
Small breaches like this one populate the daily texture of our messages. Screenshots arrive in family text threads ripped from contexts we can no longer reconstruct. A colleague drops a link into Slack with a casual “thoughts?” that reads to everyone in the channel as a pointed attack in disguise. A friend forwards a scientific study to prove they were right about something that was discussed three weeks earlier. Somebody shares a piece we wrote and misrepresents it in the caption, then tags us so the distortion lands directly in our notifications.
Underneath each of these moments is a rule being broken. We feel these rules in the flicker of hesitation before we hit send, and in the discomfort when a message arrives that we didn't want to receive. They register in gut reactions we can’t always articulate to ourselves.
We can feel a violation without being able to name the rule that was violated, because nobody ever taught us the rules. Information literacy has been the focus of educational attention for decades, but that attention has been directed primarily at how we consume information. How we treat each other during the exchange itself has received comparatively little focused attention, and the vocabulary for talking about it remains fragmented and underdeveloped.
Etiquette exists in nearly every other domain of human contact, which is what makes its absence from information exchange feel so sharp. Table manners govern how we eat together, and Emily Post built an influential twentieth-century empire on the premise that shared expectations reduce friction and build trust between people who might otherwise misread each other. Journalism and academia developed their own attribution standards over generations, though both were designed for professional settings that don’t map onto the informal channels where much of our contact with each other now takes place.
Information etiquette isn’t a term in wide use, though some of the ground it covers has been mapped under other names. Virginia Shea’s 1994 book Netiquette named a set of rules for online conduct focused mostly on early Internet contexts, and digital etiquette now often shows up in educational and workplace training. Neither has consistently centered the interpersonal dynamics of how we handle information between people who already know each other, in the messaging environments where much of our informal contact now happens. The rules named here also live inside a particular cultural context of contemporary American and Western digital communication, where directness and individual attribution are baseline expectations that vary substantially in other parts of the world.
The rules of information etiquette can be traced by looking at where they get broken. Six come up over and over across every kind of exchange between people who know each other. Each is a norm we already follow most of the time, and every one registers as felt friction the moment it gets broken.
The six rules of information etiquette
Each of the rules that follow works the same way. The sender does something small before the message goes out, like reading the article first or adding a line of framing, and the recipient feels the difference when that care is missing. Leave out the small step often enough, and the recipient starts trusting our messages less. The rules are recognizable from both directions: we've each been the sender who rushed past them, and we've each been the recipient who noticed.
We recognize these violations long before we have words for them. Most of us can recall the small drop of receiving a link that was clearly sent to score a point, or the low-grade irritation of realizing a sender never read what they shared, well before we could say what norm had been crossed. The entries below supply the vocabulary. Each one names the practice and describes what its absence feels like from the receiving end, so that both sides of every exchange become visible at once.
The moment to employ each rule is the moment before sending. Every one of the six condenses into a question that can be asked in the second before a message goes out, listed beneath each rule below.
Rule #1: Read before we share
Ask before sending: Have we read this?
When we forward a piece we haven’t read, we’re asking somebody else to invest attention in material we haven’t invested our own attention in. Sharing implies a basic endorsement, or at minimum a statement that the content is going to be useful for the recipient. The unread share tends to reveal itself: the recipient opens the piece and finds contents that don’t match how the sender framed them, or brings up the article later and discovers the sender has nothing to say past the headline. Each discovery accumulates, and over time recipients start taking that sender’s shares less seriously.
The tracking often happens below the level of conscious awareness, in the same way we register who runs late and who follows through on plans. Over time we come to know which of our people read what they send and which forward on headline alone. The habit is common enough to measure: a 2016 study by researchers at Columbia University and Inria, the French national research institute for digital science and technology, found that 59 percent of the links shared on Twitter in their dataset were never clicked. Even if the exact numbers have shifted with platform changes since, the pattern is recognizable from most people’s group chats and feeds.
Sharing without reading also changes what spreads. When a forward is a reaction to a headline, the conversation that follows is about what the headline implied instead of what the article said. The person who received the link and read the entire piece often knows more about what got shared than the person who did the sharing.
Rule #2: Don’t send an article in place of a conversation
Ask before sending: Why are we sending this?
Sharing sources is part of how disagreement gets resolved. When we lay out the reporting that changed our mind and invite a response, the article serves the conversation; the evidence gives the other person something concrete to answer. Arguments built on shared sources tend to go better than arguments built on assertion alone.
This rule covers a different send. The same article arrives bare, with no note about why we’re sending the piece and no opening for a reply, sometimes days after the argument went cold, sometimes dropped into a group chat where one particular person is expected to feel its sting. A source offered inside a conversation asks for a response. But a bare link announces instead that the sender considers the matter settled, a way of saying “I’m right” without saying the words.
Arguing this way means the argument never happens. The recipient feels the sting, the sender walks away believing the point got made, and the disagreement stays exactly where it was. A forwarded article can't do the work of a direct conversation, and every send that substitutes for that conversation makes the conversation harder to eventually have.
Rule #3: Warn people before sending heavy news
Ask before sending: Does this need a warning?
A friend texts a link to a long investigative piece about child trafficking with no framing about what’s inside. A coworker forwards a mass layoff rumor with a casual “fyi.” The emotional loads are radically different, but neither send reflects the difference in its framing; the recipient in each case has no way of knowing the depths of what they’re about to open.
Handing someone a piece of information means transferring an emotional experience along with the data. The recipient has to metabolize whatever the content contains on their own time, and often in whatever context they happen to be sitting in when the notification arrives: a doctor’s waiting room, the train home from a difficult day, the moment they were trying to fall asleep, the middle of a family dinner. The link doesn’t ask about their situation before it arrives.
A sentence of framing before a link changes how the link arrives. The framing can look like “this one’s rough, no need to open now” or a check-in about whether the topic is welcome before dropping the link at all. That small act gives the person on the other end a chance to choose when to open whatever’s inside, a chance they don’t get when a heavy link arrives bare.
Rule #4: Don’t ask for research and then reject the answer
Ask before asking: Are we open to the answer?
Someone asks for help finding information, whether a supplement is safe to take alongside a medication, or what to make of a legal situation they’ve been dealing with for months. The person asked does the work: they search, they read, they evaluate the sources, they synthesize what they find, and they bring back an answer. The person who asked then rejects the findings because the answer doesn’t match what they had already decided.
The person who did the searching finds out only when the findings get waved away: the ask sounded like a request for information while working underneath as a request for agreement. The asker usually isn’t being unfair on purpose: from the inside, wanting to be told we’re right can feel identical to wanting to know what’s true, especially when the answer we’re hoping for already feels obvious to us. Noticing which of the two requests we’re making before we ask, and receiving whatever answer comes back with an open mind, keeps the ask what the ask claimed to be.
The rule also gets broken from the other side of the exchange. Someone asks a straightforward question, and their response comes back as a curt “just Google that,” turning a genuine ask into a dismissal. But that response misses the social dimension of the original question: people often ask other people instead of searching because they want a human filter, somebody they trust to help them make sense of what they’re asking about.
Rule #5: Don’t share words without their context
Ask before sending: Is the context intact?
Screenshots are a common vehicle for this pattern across the platforms where information moves. A text message, a tweet, a headline, a data point, or a quote gets pulled from its original setting and dropped into a new one where it means something different from what it originally meant. The words themselves haven’t changed. What’s changed is the frame around them, and the frame was doing most of the work of establishing what the words meant in the first place.
Removing context produces different information that still looks like the original. The cropping can be careless, a screenshot grabbed in passing, or deliberate, when the stripped version says something the sender wants said. Either way, the person on the receiving end has no easy way of knowing what got removed, or how the removal changed the meaning of what they’re looking at. The distortion can become accepted as truth by people who receive it secondhand, and whoever wrote the original message may never get the chance to correct the record, or even know the stripped version is circulating.
Rule #6: Name the person who told us
Ask before repeating: Does the source have a name?
This rule applies to information that changes a decision or gets repeated onward. Most passing facts move through conversation without needing a name attached. But when information will steer a choice or travel onward, though, the source is part of the information: who stands behind a claim tells the listener how much to trust the claim and where to check further.
The habit stays light: saying “my friend who works in public health told me” or “I read this in a piece by so-and-so” instead of defaulting to “I heard somewhere that” or “studies show” or “apparently.” The named version tells the listener where the claim comes from, so they can judge for themselves how much trust the claim deserves. The anonymous version hands them a claim with nothing behind it, wearing the authority of research nobody can locate; the naming also keeps knowledge attached to the people who produce it.
How to repair a broken rule
Knowing the rules doesn't mean keeping them consistently all the time. We all forward without reading occasionally, and we all send heavy material without framing during moments of distraction. What counts as a violation depends on the particular two people involved: a link sent with no note could be routine between old friends but can land as rude between colleagues, and a "just Google that" from a manager lands harder than the same words from a peer. Cultural context moves the lines too, since directness that reads as considerate in one culture can come across as blunt or intrusive in another. The etiquette lives in noticing our own violations and other people's, and in what we choose to do in the aftermath.
Charitable interpretation is part of the noticing. A friend’s late-night forward with no context can be read as thoughtless, or as a gesture from somebody who was reaching out at the end of a long day. The same forward becomes a different message depending on which interpretation we choose, and we’re making that choice every time we open a notification. Interpretive charity means keeping the second reading alongside the first before deciding what a message meant, and staying open to the possibility that the person on the other end was working with different assumptions or moving too fast to notice what they’d just done.
Repair is the practice on the sending side. A brief acknowledgment that a send arrived at a bad time, or that framing got left off when the material was heavy, does the work of putting the violation into shared language. Something as simple as “sent that at a weird time; no need to respond tonight” or “sorry for dropping that without context, the topic caught me off guard” repositions the exchange without either party having to escalate.
Why these rules decide who trusts us
The rules operate one send at a time, and their effect accumulates across every exchange. A group chat becomes a place where hard news can be shared without wrecking anyone’s evening when the participants share basic norms about how sending works, and a family text thread becomes a place where questions can be asked without becoming a demonstration of who knows what. The norms make possible the trust that lets people stay in relationship with each other across the volume and speed of contemporary information exchange. Without them, the same exchanges become sources of low-grade anxiety about who’s going to send what next, and how it’s going to be framed.
There’s usually somebody in our lives whose handling of information registers as care. They pause before sending, frame heavy links, attach names to sources, and calibrate corrections in ways that leave the other person feeling seen. Their presence in our lives registers as relief, even when we haven’t yet named what exactly produces the relief.
That person isn't operating from any special knowledge; they just tend to pause at the moments the six rules describe. What changes when the rules get named, though, is that any of us can do the same noticing. The pause turns each send into a choice made with the recipient in mind. That consideration is what turns reflex into practice, and what turns a group chat, over months and years, into a place where the people we care about want to spend their attention.
A few readers have asked how to support the work outside of a subscription, so here’s another option. If something here has resonated with you or been helpful, this is one more way to show appreciation. Thank you for reading, always.
You might also like:
20 Small Acts of Media Literacy We Can Practice Every Day: From checking the date to tracing the source: building a sharper eye for information.
The information diet isn’t enough. What we need is an information village.: What changes when we go beyond optimizing our consumption and start building shared infrastructure.
The Hierarchy of Sources: A Cheat Sheet: A guide to evaluating information sources in the AI age.
The free essays are the foundation. The paid tier is where information literacy becomes a skill you can use: the Card Catalog Classroom with its searchable Reference Collection and structured lessons across four learning domains, plus biweekly AI Briefings, monthly Librarian Hotlines, and quarterly deep-dive guides.
Upgrade to paid for the full Card Catalog. Thank you for being here!
This is exactly the type of conscious centre governance the world needs.
It is, put spiritually, asking the sender to interrupt mechanical impulse. That is Gurdjieff 101.
Well done, you dont see valuable info like this often.
I've been feeling this mild friction a lot lately with AI-generated content, which probably has additional etiquette that's still emerging. I can usually tell when someone didn't really read the doc Claude generated for them or can't explain the analysis it performed, but there aren't clear workplace norms around this yet.