Youvecottmail

The garment preview shows it plainly: large, bold, white, lowercase meh. on a dark shirt. No animal. No flourish. No exclamation point hedging the bet. Just four letters and a period, set at a size that would be shouting if the word weren’t so determined not to care.

I want to take that design seriously, which is a slightly ridiculous sentence to write. But the meh shirt is doing something interesting with typography, and typography is the part of writing we notice last and read first. So let’s read it.

Editorial note: this publication and Quirky Cotton Collective share an owner. This is not an independent review.

The period is the whole joke

Strip the period and you have a word. Keep the period and you have a verdict. The lowercase meh is already deflating — it refuses the capital letter that would make it a pronouncement — but the period is what seals it. A period is the punctuation of finality. It says: this sentence is over, and so is the conversation.

Set that period in bold white type at chest scale and you have a contradiction the eye has to resolve. The word says I can’t be bothered. The typography says I went to the trouble of printing this at 72-point. That gap is the design. It’s not a slogan about apathy; it’s a slogan about the effort of performing apathy, which is a much funnier and more honest thing.

I’d call that a compressed narrative. Four characters and one mark of punctuation carry a full arc: the setup (something was expected of me), the turn (I have no strong feelings), the button (and I’m done discussing it). Good short-form writing does this — it trusts the reader to supply the context the words leave out. The shirt trusts you to know what meh means, to hear the flat tone, and to recognize the period as a door closing. If you don’t, the shirt is just a word. If you do, it’s a whole Tuesday afternoon.

Lowercase is a decision, not a default

There’s a whole tradition of lowercase as an aesthetic choice — e.e. cummings, bell hooks, the casual register of the early web — and it usually signals intimacy or refusal of authority. On a shirt, lowercase does something slightly different. It signals that the wearer is not trying to impress you. Capital letters are formal; they stand up straight and make eye contact. Lowercase slouches. Lowercase has already taken its shoes off.

That’s why the design works as a piece of reader address. The shirt isn’t talking to the room; it’s talking past the room, to the one person who gets it. It’s the visual equivalent of a deadpan aside. And the period makes sure you know the aside is finished — no follow-up question, no invitation to chat. The joke is completed by its viewer, not by the wearer. You either read it and laugh inwardly, or you don’t, and either way the shirt has already moved on.

This is the same mechanism as a good footnote, actually. A footnote is a compressed aside that trusts the reader to follow it down the page and back up again. The meh. is a footnote without a referent. It’s the aside itself, printed at the size of a headline.

What the dark ground is doing

The preview shows white lettering on a dark shirt, and that contrast matters. White on dark is high-visibility — it’s the palette of warning labels and night signage. It’s designed to be read across a room. So the shirt is simultaneously saying don’t bother me and you can read this from thirty feet away. That’s the same contradiction as the period, doubled.

I don’t think that’s an accident. The design knows that a shirt is a surface for public text, and it uses the visual grammar of public text — bold, high-contrast, centered — to deliver a private mood. It’s a billboard for a feeling that doesn’t want to be a billboard. That tension is what makes it legible as humor rather than as an actual request for solitude. If it were small and gray, it would just be sad. Large and white, it’s a performance of sadness, which is a different genre entirely.

I should be careful here: I’m describing what I see in the preview, not making a claim about the shirt’s history or its wearers. I haven’t worn it. I don’t know who buys it. I’m reading the artwork the way I’d read a book cover — for the choices the designer made and the effects those choices produce. The observation is the object; the interpretation is mine.

The word that refuses to be a brand

One more thing about meh as a word. It’s a shrug in phonetics — the vowel is flat, the consonant is soft, there’s no plosive to grab onto. It’s the sound of a balloon losing air. That makes it unusually resistant to the usual merchandise treatment. You can’t put meh on a mug with a motivational sunrise behind it. You can’t make it inspirational. The word actively repels the design language of hustle culture, which is probably why it keeps showing up on shirts and not on, say, corporate retreat banners.

That resistance is the useful argument here. A lot of slogan merchandise tries to borrow the authority of a capital letter — BOSS, FOCUS, GRIND — and the all-caps is doing the work of making a small idea feel big. The meh. shirt does the opposite. It takes a small idea and refuses to inflate it, while still using the visual scale of inflation. The result is a joke about the gap between how much we’re supposed to care and how much we actually do.

If you write for a living, you know that gap. You know the feeling of being asked to produce enthusiasm on demand, and you know the specific comedy of answering with a period. The shirt is a small, wearable version of that comedy. It’s not a manifesto. It’s a punctuation mark with a body attached.

Which is, I think, the highest compliment I can pay a piece of typography: it knows exactly how much it needs to say, and it stops.

In 1740, a printer named Samuel Richardson published a novel composed entirely of letters. Pamela, or Virtue Rewarded is not a story about correspondence with letters inserted as decoration. It is a sequence of numbered letters — LETTER I, LETTER II, LETTER III, and so on — and the reader moves through it the way a recipient moves through a mailbag: one bounded unit at a time, each with its own addressee, its own occasion, its own moment of sealing and sending.

That structure is worth examining closely, because it is the same structural question every newsletter writer faces. The container is not neutral. It shapes what can be said, how long it takes to say it, and who is imagined to be listening. Richardson’s novel is a case study in what happens when a writer chooses the container deliberately rather than inheriting whatever the platform provides.

The Printer Who Wrote Letters for a Living

The Project Gutenberg edition of Pamela includes a publisher’s note that explains the book’s origin. Richardson was a printer by trade who rose to be master of the Stationers’ Company. He became a novelist, the note says, “due to his skill as a letter-writer, which brought him, in his fiftieth year, a commission to write a volume of model ‘familiar letters’ as an aid to persons too illiterate to compose their own.”

The note continues: “The notion of connecting these letters by a story which had interested him suggested the plot of ‘Pamela’; and determined its epistolary form — a form which was retained in his later works.”

Read that sequence again. The commission came first. The container — the model letter, the familiar letter, the letter as a teachable form — came first. The story was built to fit it. This is the reverse of how we usually imagine literary invention: not a writer with something to say who then selects a form, but a form already in hand that generates the material.

For anyone who writes into an inbox, that inversion is instructive. Most of us begin with something to say and then pour it into whatever container the platform supplies: a subject line, a preview text, a body field, a send button. Richardson began with the container and discovered what it could hold.

The Letter as a Disciplined Unit

What does the letter form actually discipline? Look at the opening of LETTER I. Pamela writes to her father and mother:

“I have great trouble, and some comfort, to acquaint you with. The trouble is, that my good lady died of the illness I mentioned to you, and left us all much grieved for the loss of her; for she was a dear good lady, and kind to all us her servants.”

The letter has an addressee — two named people, her parents. It has an occasion — the death of her mistress. It has a physical constraint: paper, ink, a hand that can be seen to tremble. Later in the same letter, Pamela describes sealing coins in a pill-box so they will not chink in transit, and hiding the letter in her bosom when her master enters the room. The container is not invisible. It is part of the plot.

Then Mr. B takes the letter from her. “He took it, without saying more, and read it quite through, and then gave it me again.” The private letter has been read by someone other than its intended recipient. The container has been breached, and the breach matters.

This is the first lesson the epistolary novel teaches about serial voice: the writer is always writing to someone specific, but is also aware that the letter may travel further than intended. Pamela writes to her parents. She does not write for Mr. B. But Mr. B reads over her shoulder, and the knowledge of that possibility — not the fact of it, but the possibility — shapes what she writes and how she writes it.

The Double Audience and the Serial Voice

The letters that follow show this negotiation in action. In LETTER II, her parents write back with fear rather than comfort. They worry that she has been “set so above” herself, and they say they would “rather see you all covered with rags, and even follow you to the churchyard, than have it said, a child of ours preferred any worldly conveniences to her virtue.”

In LETTER III, Pamela responds to her father’s letter. She says it has filled her with trouble, that it has made her heart “suspicious and fearful,” and yet she hopes she will never find her master “act unworthy of his character.” The voice here is not a single register. It is intimate — she is writing to her father — and guarded, because she knows the letter may be read by others and because she is trying to manage her parents’ anxiety while managing her own.

This is the condition of the newsletter writer, though the stakes are lower and the pill-boxes are metaphorical. You write to a list. The list is composed of individuals, but it is also a collective, and any individual may forward the issue to someone you did not imagine as a reader. The voice that emerges from that condition is not a single voice. It is a negotiation between the intimacy of the direct address and the exposure of the forwardable artifact.

Richardson’s letters are not optimized for engagement. They are written to specific people for specific reasons, and the variation in length and intensity reflects the variation in occasion. Some letters are short updates. Some are long confessions. The pacing is uneven because the moments being described are uneven. A newsletter that insists on uniform length and tone is applying a platform default — consistency — that may work against the material.

What the Container Does to Pacing

The letters in Pamela are dated and sequential, but they are not uniform. LETTER IV contains a report of Lady Davers’ opinion that Pamela is “too pretty to live in a bachelor’s house,” and a note that Mrs. Jervis said Pamela “was fifteen last February.” LETTER V is a quieter letter about Mrs. Jervis using Pamela “as if she were her own daughter” and taking delight in hearing her read.

The serial rhythm is uneven by design. The writer controls when to send. The reader waits. This is a deliberate format choice, not a platform default. The letter form allows for variation because each letter responds to a specific moment, and moments are not uniform.

Compare that to the default rhythm of a modern newsletter: weekly, or biweekly, or monthly, with roughly consistent length and roughly consistent tone. The consistency is a platform default. It is not necessarily wrong, but it is inherited rather than chosen. The question is whether the consistency serves the material or merely satisfies the calendar.

The Form Was Not Incidental

The publisher’s note in the Gutenberg edition describes Pamela as a novel that “created an epoch in the history of English fiction” and that “marked the transition from the novel of adventure to the novel of character — from the narration of entertaining events to the study of men and of manners, of motives and of sentiments.”

That transition is not separate from the epistolary form. The letter is a container built for character rather than event. It records a voice in a moment, addressing a specific person, responding to a specific situation. The novel of adventure can be narrated from outside. The novel of character, in letters, must be narrated from inside a voice that is always speaking to someone.

Richardson did not invent the epistolary form. The sources do not claim he did. What the sources show is that he was commissioned to write model letters, that the commission led him to connect those letters with a story, and that the form was retained in his later works. The form was the engine, not the ornament.

The Inbox as Editorial Site

For the contemporary writer, the lesson is not “write like Pamela.” The eighteenth-century epistolary novel is evidence, not a destination. The lesson is to notice what the container is doing.

A newsletter is a letter with a list, a subject line, and a send button. The format disciplines the voice. The question is whether you are choosing that discipline or inheriting it.

Consider a practical frame: what would change if you treated each issue as a single letter to a named reader, with a beginning, a middle, and an end, rather than as a broadcast to a segment? The container is the craft. The letter form gives you an addressee, an occasion, a moment of sealing, and a moment of delivery. It gives you permission to vary length and tone because the occasion varies. It gives you a reason to end, because a letter ends.

The inbox is a site of editorial independence only if the writer treats the format as a deliberate choice. Pamela’s letters are not optimized for engagement. They are written to specific people for specific reasons. The container is not invisible. It is the thing that makes the voice possible.

Questions Writers Ask

Was Pamela published serially, in installments?

The retrieved sources do not specify whether Pamela was published in installments or only as a complete volume. The Gutenberg edition presents it as a sequence of numbered letters, and the publisher’s note describes it as a novel published in 1740. The serial structure is internal to the book — the reader experiences the letters in sequence — but the publication history of the volume itself is not established by these sources.

Did Richardson invent the epistolary novel?

The sources do not claim he did. The publisher’s note says the epistolary form was “retained in his later works” and that the novel “created an epoch” and “marked the transition” from adventure to character. Those are claims about influence and formal significance, not about priority or invention.

How many letters are in Pamela?

The table of contents in the Gutenberg edition lists letters up to LETTER XXXII, but the excerpt does not confirm the total number. The novel also includes journal entries, according to the Gutenberg summary, so the letter count is not the whole structural story.

What does this have to do with newsletters?

The connection is structural rather than historical. The letter is a container with an addressee, an occasion, and a physical form. The newsletter is a container with a list, a subject line, and a send button. Both containers discipline the voice that fills them. The epistolary novel is a useful case study because it makes the container visible — the letters are objects that can be hidden, read over a shoulder, or sealed with coins. A newsletter that treats its format as invisible inherits the platform’s defaults instead of choosing its own constraints.

Where can I read Pamela?

The Project Gutenberg edition is available at gutenberg.org/ebooks/6124. The full text is in the public domain in the United States.

Somewhere in your inbox there is a message that begins Dear [FIRST_NAME], or Hi [FIRST_NAME], or — if the platform default has been left untouched — Dear [FIRST_NAME], with the comma sitting outside the bracket like a coat left on the wrong hook. The greeting is the part everyone discusses. It is also the least interesting part of the format.

A merged message has two containers. The first is the body: the paragraphs, the greeting line, the conditional block that says since you’re in [CITY]. The second is the header section, and it is where the rules live. The personalization debate is usually conducted entirely in the first container. The more consequential decisions — who the message claims to be from, whether a reply is possible, how the reader leaves — are made in the second.

The header is a structured container, not free text

RFC 5322, the Internet Message Format specification, defines a message as header fields followed optionally by a body, separated by an empty line. Header fields are lines beginning with a field name, followed by a colon, followed by a field body, terminated by CRLF. That is the whole grammar of the top of your message. It is not a place for prose.

The standard also sets line limits: each line must be no more than 998 characters and should be no more than 78, excluding the CRLF. The conservative 78-character recommendation exists, in the standard’s own words, to accommodate user interfaces that may truncate or wrap the display of longer lines. This is worth sitting with. The limit is not about the wire. It is about the reader’s screen. A long subject line or a long display name is a bet that the client will handle it gracefully. Some do. The standard was written because some do not.

If you are choosing a merge field for a subject line, you are choosing a string that will be concatenated with other strings and then measured against a limit designed for display, not for storage. That is a format decision, and it belongs to you rather than to whatever the platform’s default template happens to do.

From and Sender are an editorial claim

RFC 5322 as updated by RFC 6854 distinguishes two originator fields. The From field specifies the author of the message — the mailbox of the person or system responsible for the writing. The Sender field specifies the agent responsible for the actual transmission. The standard’s example is a secretary sending on behalf of a principal: the principal’s mailbox appears in From, the secretary’s in Sender.

Most merged mail collapses both roles into a single From line. That is a format default, not a requirement. And the standard is explicit about the boundary: From should not contain any mailbox that does not belong to the author or authors of the message.

Read that as an editorial constraint rather than a technicality. A personalized greeting asserts authorship. When a publication merges a first name into the greeting while sending from a shared editorial mailbox, it is making two claims at once — that the message is personal, and that it is authored by the publication. The format permits both. Only one of them is stated in the field the reader sees first. Naming which claim is intended is a craft decision. It is not a deliverability decision, and no amount of subject-line testing will resolve it.

If the writing and the sending genuinely come from different parties — an editor writing under a publication’s name, an assistant sending for a principal — the format already has a field for that. Using it is a deliberate choice. Not using it is also a choice, and it is the one most platforms make for you.

The empty group: a formal option with a cost

The genuinely interesting merge artifact in the retrieved standards is group syntax. RFC 6854 updates RFC 5322 to allow group syntax in the From and Sender fields, as well as in Resent-From and Resent-Sender, in certain situations. The standard’s own example is an automated nightly monitor program, presented like this:

From: Nightly Monitor Robot:;

The empty group after the colon means the message presents itself as coming from a system with no replyable address. Recipients’ email clients will not allow them to reply in the first place. The standard notes that such messages commonly include a valid, replyable address that discards replies — and that recipients who do reply might be unaware their replies will be discarded. The empty group is a way of being honest about that.

It is also a formal option with a cost attached, and the standard says so plainly. Group syntax is characterized as Limited Use. User agents should not permit its use in outgoing messages. Senders need to be aware that using groups in the From field might adversely affect deliverability.

For a writer, this is the most useful kind of artifact: a documented option that most platforms will never offer, with the trade-offs stated in the same document that permits it. You are unlikely to need it. You are more likely to need to know it exists, so that when a platform collapses every originator into a single friendly name, you can see what has been decided on your behalf.

The exit is part of the format

RFC 8058 describes a method for signaling a one-click function for the List-Unsubscribe header field. The requirements are specific. A sender enabling one-click unsubscription places one List-Unsubscribe header field and one List-Unsubscribe-Post header field in the message. The List-Unsubscribe field must contain one HTTPS URI. The List-Unsubscribe-Post header must contain the single key/value pair List-Unsubscribe=One-Click. The message must have a valid DKIM signature covering at least those two headers.

The POST request must not include cookies, HTTP authorization, or any other context information. The sender must not return an HTTPS redirect, because redirected POST actions have historically not worked reliably. And the receiver must not perform the POST without user consent.

Read this as the counterpart to the greeting. The container has a provision for the reader leaving, and that provision is engineered rather than appended. A publication that treats the inbox as a site of editorial independence should treat the reader’s departure with the same deliberateness as the reader’s arrival. The unsubscribe path is not an afterthought bolted onto the format. It is part of the format, and the standard treats it with the same specificity as the address fields.

What the merge actually is

The mail merge is usually told as a story about personalization — a name swapped into a greeting line. The standards suggest a different and more useful account. The merge is a set of decisions about which fields you fill and which you leave honest. Personalization at scale is bounded by the address syntax. The unsubscribe path is bounded by the same header section that carries the greeting.

A hypothetical illustration, clearly labeled as such: a small publication merges a first name into its greeting while sending from a shared editorial mailbox. It is making two claims at once. The format permits both, but only one is stated in the field the reader sees first. Naming which claim is intended is the work. The platform default will not name it for you.

The container disciplines the content. That is not a constraint to work around. It is the material you are working with.

Questions readers ask

Can I use group syntax in my newsletter’s From field? The standard permits it in certain situations, but characterizes it as Limited Use, advises that user agents should not permit it in outgoing messages, and warns that it might adversely affect deliverability. Most newsletter platforms will not expose the option at all. If you need a message that cannot be replied to, the empty group is the documented form; whether it is the right choice for your publication is a separate question.

Does the 78-character line limit apply to my subject line? RFC 5322 states that each line must be no more than 998 characters and should be no more than 78, excluding the CRLF. The recommendation exists to accommodate user interfaces that may truncate or wrap longer lines. Subject lines are not header fields in the same sense, but the reasoning — display, not storage — applies to any string the reader sees first.

What does one-click unsubscribe require? Per RFC 8058: one List-Unsubscribe header with one HTTPS URI, one List-Unsubscribe-Post header containing List-Unsubscribe=One-Click, and a valid DKIM signature covering both headers. The POST must not carry cookies or context information, and the sender must not redirect it.

Should I use Sender if I’m sending from a shared mailbox? The standard distinguishes the author of the message from the agent responsible for transmission, and its example is a secretary sending for a principal. If the writing and the sending genuinely come from different parties, the format has a field for that. Whether your platform exposes it is a separate matter.

There is a particular kind of silence that follows a post. You press publish, the thing goes out into the feed, and then you wait. The silence is not empty; it is full of other posts, arriving in a churn of algorithmic sorting. You have not written to anyone. You have posted at everyone, and the platform has decided who, if anyone, will see it.

Writing to people instead of posting at them is a format choice, not a moral one. It means choosing the inbox over the feed, the address over the broadcast, the reply over the reaction. It means treating the email list not as a distribution channel to be optimized but as a site of editorial independence. The container disciplines the content: a post is shaped by the feed’s incentives, while a letter is shaped by the reader’s attention. This article is about why that distinction matters, how it shows up in the artifacts of digital correspondence, and what it asks of writers who want to make deliberate choices rather than inherit defaults.

What “Writing to People” Actually Means

Writing to people is a practice with a long material history. It is not new, and it is not a reaction against technology. It is a way of using technology that keeps the reader in view. The opposite — posting at people — is a broadcast model where the platform mediates the relationship, decides the audience, and rewards certain kinds of engagement over others.

The distinction is not about email versus social media. You can post at people in an email newsletter, and you can write to people in a public post. The difference is in the address. A letter has a recipient. A post has an audience. A recipient can reply; an audience can react. A recipient is a person you can name; an audience is a number you can track.

This matters to writers because the format shapes the writing. If you know you are writing to a specific person, you make different choices. You explain more. You assume less. You do not write for the algorithm; you write for the reader. The inbox is a place where the reader has already opted in, where the relationship is direct, and where the writer can be deliberate about what arrives.

The Feed and the Inbox as Different Containers

Every container has a discipline. A feed is designed for scrolling. It rewards novelty, brevity, and emotional immediacy. It is a stream, and streams are hard to write in. The feed’s default is the post: a unit of content that competes for attention in a continuous flow. The writer who posts is writing into a system that will decide how the post is seen, how long it lives, and who it reaches.

An inbox is designed for reading. It is a queue, not a stream. It has a beginning and an end. It is a place where the reader has chosen to receive something, and where the writer can assume a certain amount of attention. The inbox is not a perfect container — it is full of noise, and the reader’s attention is finite — but it is a different kind of container. It disciplines the content differently.

The feed’s default is the reaction: the like, the share, the quick reply. The inbox’s default is the reply: a considered response, often longer, often private. The feed optimizes for reach; the inbox optimizes for relationship. Neither is inherently better, but they produce different kinds of writing. If you want to write to people, you have to choose the container that supports that.

Artifacts of Address: A Short Material History

The history of writing to people is a history of formats. Consider the postal reform of 1840 in Britain, when the Penny Black introduced uniform penny postage. Before that, postage was paid by the recipient, and the cost was high. The reform shifted the cost to the sender and made sending cheap. This changed what people wrote. Letters became more frequent, more casual, more like conversation. The container — cheap, prepaid postage — disciplined the content. People wrote more because it was easier to send.

Consider the RFC 822 standard, published in 1982, which defined the format of email messages. It established the header fields — From, To, Subject, Date — that we still use. This was a technical decision, but it had editorial consequences. The Subject line became a place for a summary. The To field made the recipient explicit. The format assumed a direct address, not a broadcast. Email was designed as a letter, not a feed.

Consider the mailing list, a tool that emerged in the 1970s and 1980s. It allowed one message to be sent to many people, but it preserved the address. Each recipient received the message in their inbox, and could reply to the list or to the sender. The mailing list was a hybrid: a broadcast that still felt like a letter. It was a container that disciplined the content toward conversation, not performance.

Consider the newsletter, a format that has been reinvented many times. The email newsletter is a direct descendant of the printed newsletter, which was itself a way of writing to a defined group of people. The newsletter’s container — a regular issue, a consistent format, a direct address — disciplines the content toward curation and voice. It is not a feed; it is a publication. The writer who sends a newsletter is writing to people who have asked to receive it.

These artifacts are evidence, not destinations. They show that the container matters. The format you choose shapes what you can say and how it will be read. The past does not tell us to go back; it tells us that the choices we make about format are editorial choices.

Why the Inbox Is a Site of Editorial Independence

The inbox is not owned by the writer, but it is not owned by the platform either. It is a space where the writer and the reader meet directly. The writer can choose the format, the frequency, and the voice. The reader can choose to open, to read, to reply, or to unsubscribe. This is a different power dynamic from the feed, where the platform sets the rules and the writer competes for attention.

Editorial independence means the writer decides what to publish, not the algorithm. It means the writer can write a long piece, or a short one, without worrying about whether it will be seen. It means the writer can assume a relationship with the reader, rather than treating every post as a cold start. The inbox supports this because it is a direct channel. The writer is not renting space on someone else’s feed; they are sending a letter to someone who has agreed to receive it.

This is not a utopian claim. The inbox has its own problems: deliverability, spam filters, the endless battle for attention. But the inbox is a place where the writer can be deliberate. The feed is a place where the writer is subject to the platform’s defaults. If you want to write to people, the inbox is a better container for that.

Practical Choices for Writing to People

If you want to write to people instead of posting at them, here are some practical choices. These are not rules; they are formats to consider.

Choose a direct address

Write to a specific person, even if you are writing to many. Use “you” and mean it. Avoid the royal “we” unless you are actually speaking for a group. The direct address is a discipline: it forces you to imagine a reader and write for them.

Use a consistent format

A newsletter with a consistent format — a regular issue, a familiar structure — disciplines the content. The reader knows what to expect, and the writer has a container to fill. This is not about rigidity; it is about creating a recognizable publication. The format is a promise to the reader.

Write for the reply

If you want a conversation, make it easy to reply. Ask a question. Invite a response. The inbox is designed for replies; use that. A post that invites reactions is different from a letter that invites a reply. The reply is a signal that you are writing to a person, not posting at an audience.

Respect the reader’s attention

The inbox is a finite space. Do not fill it with noise. Write something worth reading. This is not about length; it is about care. The reader has given you their attention; use it well.

Own the relationship

The inbox is a direct channel. Do not treat it as a place to dump content from other platforms. Write something that belongs in the inbox. The container disciplines the content: if it feels like a post, it probably is.

Tradeoffs and Cautions

Writing to people is not a cure-all. It is slower. It requires a list, which requires trust. It does not have the reach of a feed. It can be lonely: you send a letter and wait for replies. It can be hard to grow. These are real tradeoffs. The feed is better at discovery; the inbox is better at relationship. The choice depends on what you want to do.

There is also a risk of nostalgia. The past is not a destination. The postal reform of 1840 was not a golden age; it was a specific response to specific conditions. The inbox today is not the same as the mailbox then. The point is not to go back; it is to see the container clearly and choose deliberately.

Finally, writing to people is not about being anti-platform. It is about being pro-reader. The platform is a tool; the reader is a person. If you want to write to people, you have to choose formats that keep the reader in view. That is an editorial choice, and it is available to anyone who wants to make it.

FAQ

What does “writing to people” mean in practice?

It means choosing formats that address a reader directly, such as an email newsletter, a personal letter, or a direct message. It means writing for a recipient, not an audience. It means inviting replies, not just reactions.

Is email better than social media for writers?

Not inherently. Email is better for direct relationship and editorial independence; social media is better for discovery and reach. The choice depends on your goals. The key is to choose deliberately, not by default.

How do I start writing to people if I already have a social media following?

Start a newsletter. Invite your followers to subscribe. Write to them directly. Do not just cross-post; write something that belongs in the inbox. The format will discipline the content.

What are the risks of writing to people?

It is slower, harder to grow, and requires trust. You may get fewer replies than you expect. But the replies you get will be from people, not metrics.

Does writing to people mean I should stop posting?

No. It means you should know the difference. Post when you want reach; write when you want relationship. The container disciplines the content, so choose the container that fits your intent.

If you want to go further, consider the follow-up question: what does a deliberate newsletter format look like? That is a topic for another issue. For now, the case is simple: write to people. The inbox is waiting.

I have a copy of The Complete Letter-Writer on my desk. Not a first edition — a 1980s facsimile of a mid-Victorian printing. I keep it within arm’s reach because it’s the most quietly radical book on writing I own, and almost none of its advice would survive a modern editorial meeting.

What it contains instead are salutations.

Pages of them. Different openings for a letter to your father, your solicitor, a distant acquaintance, a close friend, a creditor, a governess seeking a new position, a clergyman, a lover. Each one encodes a relationship. Each assumes that how you begin a letter declares — before a single substantive word — who you are to the person reading, and who they are to you.

Most newsletters I receive begin with “Hi there” or “Hey friends” or, increasingly, nothing at all.

Let me be precise about the artifact, because the argument hangs on it. The salutation is the first written word of a message that names or addresses the recipient. It is not a subject line, which is a title. It is not a greeting, which is a performance. It is the specific moment in correspondence when the writer declares: I see you. I know who you are. Here is how I’m framing the relationship between us for the duration of what follows.

That declaration used to matter enormously. It still does, though most platforms would prefer we not notice.

What the Victorians Knew About Opening a Letter

The Victorian letter-writing manual was not a casual genre. It flourished after the 1840 Penny Post reform, when a standardized postal rate made private correspondence accessible to working and middle-class households for the first time. People who had never written letters suddenly needed to write them — to employers, creditors, distant family, potential suitors — and the manuals existed to teach them how.

What the manuals taught, primarily, was that the opening was a social contract.¹ A letter to a social superior required a formal salutation: My Lord, Reverend Sir, Madam. A letter to an equal required something measured: Dear Mr. Blackwell, My Dear Mrs. Hartley. A letter to an intimate friend or family member permitted warmth: Dearest Eleanor, My Beloved Sister.

The distinction between Dear and My Dear was not decorative. My Dear signified greater intimacy; Dear alone was more formal. That possessive My was the difference between a colleague and a confidante. A person who wrote My Dear Sir to a near-stranger would be committing a social error — presumptuous, overfamiliar. A person who wrote merely Sir to a close friend would be delivering a snub.

The comma-versus-colon question, which still surfaces in business correspondence guides today, descends directly from these manuals. A colon after a salutation — Dear Sir: — was the formal mark, indicating a business or official register. A comma — Dear Eleanor, — indicated personal correspondence. The punctuation was a tonal signal, not a stylistic preference.

What strikes me reading these manuals now is how seriously they took the idea that the opening of a letter was an editorial decision. The writer was choosing, from a finite set of recognized forms, the one that accurately described the relationship. Getting it wrong was not a grammatical error. It was a misrepresentation of the social world.

The Flattening

Email clients, when they arrived in the 1990s and 2000s, inherited almost none of this specificity. What they inherited was a default. Dear was too formal for the new medium — too associated with physical letters and official correspondence. Hi was friendly but generic. The salutation became a courtesy rather than a declaration, something you did because the template had a space for it, not because it carried meaning.

Most email clients I’ve used, from Pine and Eudora through to Gmail and Superhuman, treat the salutation as optional or as a field to be auto-filled with a personalization token. The infrastructure of email — the merge field, the template, the greeting block in the newsletter tool — is designed to make the salutation automatic. You insert {{first_name}} and move on to the body. The software does not ask whether Hi {{first_name}} accurately reflects your relationship with the reader. It doesn’t ask because it’s not a question the software is built to consider.

The result is a flattening. Where the Victorians had a dozen salutations calibrated to a dozen degrees of intimacy, the modern newsletter writer inherits two or three: Hi [Name], Hey there, or nothing. The range of declared relationships has collapsed from a spectrum to a binary — named or unnamed, personal or broadcast.

And here’s the problem: a newsletter is not a broadcast. Or rather, the best ones aren’t. A newsletter that feels like a press release sent to a list is one that readers archive rather than read. According to a Pew Research Center report on email newsletters as a news source, three in ten U.S. adults say they at least sometimes get news from newsletters, but many subscribers don’t read most of the newsletters they receive. The opening salutation is the first moment where a writer either earns a reader’s attention or confirms that what follows is skippable.

What the Salutation Actually Does

Let me break down the rhetorical work a salutation performs, because I think it’s more than most writers realize.

First, it declares the relationship. Dear Dr. Marsh says: I know you, I respect your title, this is professional correspondence. Hi Sarah says: I know you, we’re on a first-name basis, this is casual. Hey there says: I don’t know you specifically, but I’d like you to think I do. Reader says: I know you only as a reader, and I’m choosing to address you in that role rather than pretending otherwise. Each of these is a different social contract, and each sets a different expectation for what follows.

Second, it sets the register. A formal salutation primes the reader for formal prose. A warm one primes them for warmth. A witty one — and I’ve seen a few newsletter writers who do this beautifully — primes them for wit. Skip the salutation and you’ve left the register undefined, which means the reader will impose one. They’ll default to whatever they expect from a newsletter, which is usually: something promotional.

Third, it signals whether the writer sees a person or an audience. This is the one that matters most for independent newsletter writers. Hi everyone addresses a crowd. Dear reader addresses a role. Hi Margaret addresses a person. The difference between a person and an audience is the difference between a letter and a press release, and the salutation is where that difference gets declared.

When a newsletter opens with Hi there and then proceeds to address me by first name three paragraphs in, I notice. The writer is using personalization tokens — I know this because the capitalization is slightly off and because no human being has ever called me there in a letter. The salutation is a tell. It tells me that the writer is using a tool that addresses me, not choosing words that address me.

The Named Greeting and the Reader’s Trust

Trust in media is not an abstraction. It is built in small moments — the subject line that doesn’t oversell, the paragraph that doesn’t pivot to a product, the salutation that sounds like it was written by a person who knows what they’re doing. The same Pew Research Center data on news habits and media engagement shows that a majority of Americans express low confidence in journalists to act in the public’s best interest. The salutation will not fix that. But it is one of the few places where an independent writer, working outside institutional media, can immediately signal a different kind of relationship — one built on direct address rather than institutional authority.

The newsletters I trust most are the ones whose writers seem to have considered every line, including the first one. Craig Mod’s Roden newsletter often opens with a simple Friends — which works because he’s established, over years of correspondence, that the relationship is genuinely one of friendship, or something close to it. Robin Sloan’s Year of the Newsletter dispatches open with Dear friend — a slightly archaic, slightly formal choice that signals you’re about to read something considered. Anne Helen Petersen’s Culture Study letters frequently open with Hi everyone — which works because the newsletter is explicitly a community publication, and the salutation matches the format.

What these have in common is that the salutation matches the content. The writer has chosen an opening that accurately describes the relationship the rest of the letter will enact. When the salutation is inherited from a template rather than chosen, it almost always mismatches. Hi there followed by a 2,000-word essay on media infrastructure is a mismatch. The salutation promised casual and the content delivered considered. The reader feels it, even if they can’t name it.

A Practical Note on Choosing

I want to offer something concrete here, because I think the case for deliberate salutation is stronger if I can show what the practice looks like.

The first question is whether to name the reader at all. Personalization tokens — {{first_name}} — are technically easy and editorially complicated. If you use one, you’re claiming a familiarity you may not have. If you don’t, you’re choosing to address a role rather than a person, which can be more honest. Dear reader is not a failure of personalization. It’s an acknowledgment that you don’t know me, and that you’re not going to pretend otherwise.

The second question is what register the salutation sets. If your newsletter is a formal essay publication, a formal salutation — Dear reader, Dear subscribers — sets the right expectation. If it’s a casual dispatch, Hi or Hey may work, but only if the rest of the writing matches. If it’s a personal letter that happens to go to a list, you might consider addressing it to a specific person — a real one, not a composite — and letting the reader understand that they’re reading over someone’s shoulder. This is what Virginia Woolf did in her diary-letters, and what some of the best personal newsletter writers do now.

The third question — and this is where I think the analogy to fiction writing is most useful — is what to call the person on the other end. In a novel, a character’s first spoken line does enormous work. It establishes voice, class, temperament, the nature of the scene. A salutation does the same thing for a newsletter. The name you choose to call your reader — friend, reader, colleague, everyone, or their actual first name — is a small editorial decision with outsized consequences, and it deserves the same deliberation a novelist gives a character’s entrance. Novelists often experiment with character name generators as a way of forcing themselves to consider how naming conventions signal class, origin, and relationship — and the same discipline transfers to the question of what to call the person reading your newsletter. Some writers I know approach their salutation the way a fiction writer approaches a character name generator — not because they’re writing fiction, but because the act of choosing a name deliberately, with attention to context and register, is the same editorial muscle whether you’re naming a character or addressing a reader.

That same discipline applies to naming decisions: before publishing, editors need a way to test labels, roles, and public-facing language stay consistent, which is where how Unsloppy AI Writing App fits the writing workflow can function as a planning aid rather than a substitute for domain evidence.

The point is not that you need a tool to choose a salutation. The point is that the choice deserves the same seriousness. Hi there is a default. Dear reader is a position.

What We Lose

When the salutation disappears — when it’s skipped, automated, or reduced to a personalization token — we lose more than a social convention. We lose a form of editorial intention.

The Victorians understood that the opening of a letter was where you declared the relationship. Not the content — the relationship. The container before the contents. And the container, as I keep arguing in this newsletter, shapes the contents more than most writers are willing to admit. A letter that opens My Dear Mrs. Hartley is a different letter from one that opens Dear Subscriber, even if the body text is identical. The salutation has already told the reader what kind of correspondence this is, what register to expect, and whether the writer sees them as a person or a line on a list.

The newsletters that feel like mail — the ones I read first, the ones I trust — are the ones where the writer has chosen the salutation with the same care they chose everything else. Not because the salutation is the most important part of the letter. Because it’s the part that tells me whether the rest is worth reading.

Let me put it another way. The salutation is the first place a writer can betray carelessness. It’s also the first place a writer can demonstrate that they’ve thought about who’s on the other end. In a medium where most writers are competing for attention, the writer who has thought about the salutation has already done something most haven’t. They’ve begun the correspondence as if it were a correspondence.

¹ The Victorian manuals I reference here include The Complete Letter-Writer (various editions, 1840s–1880s) and The Friendly Letter-Writer (c. 1855). Both prescribed salutations by rank, intimacy, and purpose. The comma-colon distinction is documented across multiple editions and was standard advice through the early twentieth century.

—

What do you open your newsletters with, and why? I’m genuinely curious, because I suspect most of us inherited our salutations the way we inherited our fonts — from a template we never chose. I’d like to hear from writers who’ve thought about this, and from readers who’ve noticed when a salutation landed right or wrong. Hit reply. I read everything.