Writing Now, Posting Later

The composer's schedule picker open, showing a future date and time selected for a written-but-unpublished post

Write it now, pick when it goes out, close the laptop.

Part 7 of 7: A Field Guide to Messages

Last persona of the series: the conference speaker with a launch window. She has a talk landing Tuesday at 10 a.m., and she knows exactly what she wants to post the moment it does: the slides, the repo, a thank-you to the room. She also knows she will be standing on a stage at 10 a.m. Tuesday with sweaty palms and no free hands. The post needs to go out at the worst possible moment for her to be posting it.

So she writes it Sunday night, when she is calm and the words are good, and she tells it to publish Tuesday at 10:05. Then she goes to bed. That is scheduling, and it is the last of the Subscriber-gated pieces in this series, sitting alongside cross-posting and media behind the same subscription line.

Set a time in the future

In the composer's settings area there is a schedule control. Pick a date and time, and instead of publishing now, the post is held with a scheduledAt stamp for when you chose. It has to be in the future (the app will not let you schedule a post into the past, which sounds obvious until you have fat-fingered a date). Until that moment arrives, the post is yours and yours alone: it shows up in your own scheduled queue, not in anyone's feed.

There is a view for exactly that queue, so the speaker is not trusting a black box. She can pull up what she has scheduled for today, this week, or this month, in the order it will go out, and confirm the launch post is really sitting there armed for Tuesday.

A scheduled-posts queue listing upcoming posts ordered by their send time, each with a Scheduled badge

The queue, earliest first. Proof the thing you wrote Sunday is really going out Tuesday.

The every-minute heartbeat

Here is the part I like as the person who built it. There is a cron job named publish-scheduled-messages, and it runs every single minute. Every minute it wakes up, looks for posts whose scheduled time has arrived, and publishes them. That is why the speaker can pick 10:05 and trust it means 10:05, not "sometime this hour." The resolution of the whole system is one minute, because the heartbeat is one minute.

And it does not just drop the post onto her InterlinedList timeline. When she scheduled it, she also picked her cross-post networks, and that choice was stored right alongside the post. So when the cron fires Tuesday morning, it publishes here and runs the cross-posts: the launch note lands on Bluesky, Mastodon, LinkedIn, and X at 10:05, threaded to fit each one, while she is still walking off the stage. She wrote it once, on Sunday, and the machine did the loud part on Tuesday.

A couple of honest edges, because they are the kind of thing that surprises people. Scheduling is for original posts. You cannot schedule a reply (replies are meant to be part of a live conversation) and you cannot schedule a plain repost. And a scheduled post is a promise the system keeps at the future time, not a draft you keep editing forever: it is written, queued, and fired. If plans change, you cancel it before it goes out.

Where this leaves the box

Seven posts ago this was a text field with a checkbox. Now the speaker uses the same field to draft a launch on Sunday, pick four networks and a Tuesday-morning time, and let a once-a-minute cron deliver it to the whole internet while she is otherwise occupied. Same box. She never learned a second tool. She just kept discovering that the box did more than she asked it to.

That is the thing I want to leave you with, and it is not a summary so much as an invitation. The next time you open that box to dump a private note, notice that you are standing at the bottom of a ladder that goes all the way up to scheduled four-network syndication, and that every rung uses the same three fields you started with. Start at the bottom. The box will be there when you want to climb.

Adron