2026-08-13
Cross-post to Mastodon, Bluesky, and X without opening three apps
Write the short version once, change only what has to change, then publish or schedule from one screen.
The usual advice is to be native on every platform. The usual result is you post to one network and forget the rest. I did this for years. A thought would land on X, a screenshot might make it to Instagram two days later, and Mastodon would get nothing because I was already tired of copying.
Bluesky made that worse, in a good way. Suddenly there was another short network I actually wanted to be on, with a different audience and a similar character limit. The ritual became: write it, paste it, trim it, post it, open the next app, paste it again, notice the link preview is wrong, fix it, post it, feel done, remember Mastodon exists, decide tomorrow is fine. Tomorrow was not fine.
Write the short take first
A better default is boring. Write the short version once, then change only what has to change. X and Bluesky want the short take. Mastodon can take a slightly longer one, and people there notice if you dump a tweet with a tracking redirect still in it. LinkedIn can take the argument, including the context you would never fit in 280 characters.
I do not try to make one sentence that is equally good in all four places. That sentence does not exist. What exists is a core claim, then a few edits. Maybe you drop a hashtag. Maybe you add the why. Maybe you swap a joke that only works on X for a plain sentence that will still make sense in a Telegram channel next week.
In PostBroadcaster that is one screen. Connect the accounts you actually use. Write the default caption. Open the override where the limit or the tone is different. Publish now, or pick a time. You do not open three apps, and you do not keep a notes file of versions.
Platform rules stay visible
I still treat platform rules as rules. Instagram needs media. Nostr accounts that sign in the browser still need you to click sign. Those are not product theater. If a network will reject the post, the composer should say so before you hit send, not after a spinner and a vague error.
The same is true of length. A tool that lets you type 2,000 characters into an X field and then fails at publish time is not being flexible. It is hiding the brief. I would rather the counter and the override sit next to the account, so the disagreement is visible while you are still writing.
If you only ever post to one place, you do not need this. If you keep meaning to post to the others and never do, this is the workflow I wanted when I got tired of the paste ritual.
Try the composer
Sign in with Google, connect the accounts you actually use, and publish or schedule.
Get started