Cross-Posting to Bluesky and Mastodon Without Annoying Anyone

Running Bluesky and Mastodon side by side sounds like it should be trivial. Both are open, both are text-first, and both absorbed roughly the same crowd leaving roughly the same place at roughly the same time. In practice they are two different cultures with two different sets of rules, and the fastest way to lose ground on both at once is to pipe identical text into each and walk away.

There is a way to do this that saves real time and does not get you muted. It requires knowing what genuinely differs between the networks, and taking Fediverse crossposting norms more seriously than most tools will encourage you to.

Neither network gives you a clean native path. Bluesky has no built-in scheduler at all, so posts publish the instant you submit them. Mastodon is stranger: a fully functional scheduler exists inside its code, and its API has accepted a scheduled publish time for years with a minimum lead time of five minutes, but the official web interface and official apps still give you no way to reach it. On one network the feature does not exist; on the other it exists and is not exposed.

Then there is the shape of Mastodon itself. There is no single Mastodon. There are thousands of independently operated servers with their own rules, their own moderators and their own tolerance for automated posting. Behaviour that passes without comment on one instance will earn you a warning on another, and neither server is wrong.

Bluesky caps posts at 300 characters, counted as graphemes, so a multi-part emoji counts as one. Mastodon defaults to 500, but that number is set by whoever runs your server. Admins can raise it and plenty do, with some instances running to a thousand characters or well beyond. Never assume 500 without checking your own instance.

Links behave differently too. On Bluesky the URL sits in your post text and counts against your 300. On Mastodon every link counts as a flat 23 characters no matter how long it is, which is why link shorteners are pointless there and mildly suspicious looking.

The practical rule: write to 300 and the same text works in both places. Write to 500 and you will be hacking it apart at the last minute. If a thought genuinely needs the extra room, write the Mastodon version properly and write a tighter Bluesky version. It takes ninety seconds and both read better for it.

Both networks care about image descriptions, and the Fediverse in particular treats alt text as a baseline courtesy rather than a nice extra. There is an established convention where people who cannot write their own descriptions post asking for help with a dedicated hashtag, and strangers reply with one written for them. That tells you how normalised the expectation is.

This matters specifically for crossposting, because a lot of automated pipelines drop alt text on the floor. If an image carries meaning rather than decoration, and you are not certain your tool passes descriptions through, publish that one natively and keep the queue for text.

This is the difference people get wrong most often. Mastodon has a free-text content warning field: you write a short label, the post collapses behind it, and the reader chooses to expand. There is a strong tradition that those who are able to should use one for emotive subjects such as politics or religion, on top of the more obvious cases like distressing news, spoilers and anything not safe for work.

Bluesky has self-labelling, but it is a fixed set of adult content categories rather than an arbitrary warning you can write yourself. So content warnings do not translate between the two networks. If your material regularly touches subjects your instance expects a warning on, add the warning to the Mastodon version by hand, or keep that category out of the queue entirely.

The framing worth adopting is that a content warning is an accessibility feature, not a penalty. It makes a post readable by people who would otherwise have to scroll straight past it, in the same way alt text makes an image readable by someone using a screen reader.

Most Mastodon instances do not index full-text search by default, so hashtags are the actual discovery mechanism rather than decoration. Two or three relevant ones, written in CamelCase so screen readers can pronounce them. Bluesky does have search, and a stack of hashtags there reads as imported marketing. Same symbol, different job.

This is the rule that matters more than every other rule combined. The Fediverse guidance on crossposting is blunt about it: the practice becomes controversial when you are posting to Mastodon without interacting on Mastodon at all, and some servers specifically ban accounts that behave that way. Your followers will reply to you, and a feed that never replies back is precisely the behaviour people object to. Ten minutes a day of genuine conversation buys you an enormous amount of latitude on everything else.

Mastodon lets you mark an account as automated in its profile settings. If you truly cannot monitor replies, the recommended practice is to set that flag so people know you are posting in one direction only. It costs nothing, it is honest, and it defuses most of the irritation before it starts.

Instance rules are not boilerplate. Some servers ban crossposting outright, some ban unattended accounts, some require content warnings on specific topics. Read the rules page of your home server before you queue a month of content. If your posting style genuinely conflicts with your instance, the right move is to find a server whose culture fits, not to argue with volunteer moderators about it.

PostSpoke handles the first four in one place. Bluesky connects with a handle and App Password, Mastodon connects by instance domain with the app registering itself against your server dynamically so there is no developer account to set up, and both sit in the same composer and calendar. Credentials are stored encrypted, and both networks are live today rather than sitting on a roadmap.

Cross-posting Bluesky and Mastodon is a scheduling problem with a manners problem attached, and the manners problem is the harder of the two. Solve it and the scheduling is fifteen minutes of setup. Skip it and no tool will help you, because the Fediverse has a long memory for accounts that broadcast and never listen.