Posting windows

Pick the next good slot. In your time zone, not the server’s.

Every platform has hours where attention is cheap and hours where it is not. Postonus carries a set of recommended windows per platform, each weighted by how strong it is, and can drop a post into the next one — with a consensus window when you are posting to several platforms at once.

Schedule at the next window

Available in the composer, CLI, and MCP.

Capabilities

What you get with Posting times.

Windows, not single times: A recommendation is a range on a given weekday, not a magic minute. Treating it as a range is honest about the precision available and leaves room to space several posts inside one window.
Weighted by strength: Each window carries a strength from 1 to 5, so a Tuesday morning on LinkedIn is not presented as equivalent to a Saturday. Weak windows are still offered, just ranked lower.
Consensus across platforms: Posting to four platforms at once asks for a slot that suits all of them. The recommendation is computed across the set rather than picking one platform’s best hour and hoping.
Reachable from every surface: The composer offers the next window, postonus best-times prints them, and an assistant can ask for them over MCP with get_best_times. Same data behind all three.

What a recommendation is

A window, on a weekday, with a strength:

LinkedIn
  Tue 08:00–10:00   strength 5
  Wed 08:00–10:00   strength 5
  Thu 09:00–11:00   strength 4
  Tue 12:00–13:00   strength 3

Ranges rather than exact times, for two reasons. It is more honest about how precise this kind of guidance can be. And it gives bulk scheduling somewhere to put several posts without stacking them on the same minute.

Being straight about the source

These are platform-level recommendations — curated guidance about when each platform generally sees more attention. They are not derived from your account's own performance history.

We would rather say that plainly than imply a personalisation that is not there. Plenty of tools present a generic table as though it were computed from your data. If your audience sits in one time zone, or your niche is genuinely nocturnal, your own observed results beat any of this, and you should schedule accordingly.

What the windows are good for is the cold-start problem: a new channel with no history, or a platform you have never posted to seriously, where a sensible default beats a guess.

Consensus for multi-platform posts

Posting to LinkedIn, X, Bluesky, and Threads at once creates a small optimisation problem, because their good hours do not coincide. Taking LinkedIn's best slot might land you in one of the worst on the others.

So the recommendation is computed over the set you selected, weighted by each window's strength, and returns slots that work reasonably for all of them. If you would rather optimise per platform, schedule them separately — nothing forces one time across channels.

For a channel you already post to regularly, trust your own numbers over any recommendation. These windows are a starting point, and the strength values are guidance rather than measurement.

From the terminal and from an assistant

postonus best-times --to linkedin,x
postonus post "shipped it" --to x,linkedin --optimal

--optimal resolves the next recommended window for the channels you named and schedules there. An assistant connected over MCP can ask the same question with get_best_times before proposing a time, which is what makes "schedule this for a good slot tomorrow" a sensible request to make of it.

Found this useful? Pass it on.

Questions

Frequently asked questions Everything the first evaluation usually needs.

Where do the recommended times come from?: They are a curated set of windows per platform, each with a day, a time range, and a strength from 1 to 5. They are published guidance about when engagement is generally higher on each platform, not a reading of your own account’s history.
Are these based on my own analytics?: No, and it is worth being clear about that. They are platform-level recommendations. If your audience is in an unusual time zone or your niche behaves differently, your own results should override them.
What time zone are the windows in?: They resolve in your time zone, so a 09:00 window is 09:00 where you are. Scheduling is time-zone aware throughout, including across daylight-saving changes.
What happens when I post to several platforms at once?: You get a consensus window computed across the platforms you selected, rather than one platform’s peak that happens to be a poor slot for the others.
Can I ignore the recommendations?: Yes. Pick any time you like — the recommendation is a default, not a constraint.
Can I get the windows outside the dashboard?: Yes. postonus best-times --to <platforms> prints them in a terminal, and an AI assistant connected over MCP can call get_best_times. Both read the same data the composer does.

Keep reading

Schedule at the next window

Available in the composer, CLI, and MCP.

Schedule at the next window