Post Once, Show Up Everywhere

The advanced composer with cross-post toggles for Bluesky, Mastodon, LinkedIn, and X all switched on beneath the text box

One post, four networks selected. Write it once, it lands on all of them.

Part 5 of 7: A Field Guide to Messages

Meet the creator. He writes a good short update maybe twice a day, and until recently he published each one by hand into four different apps. Open Bluesky, paste, post. Open Mastodon, paste, post. Open LinkedIn, paste, reformat because LinkedIn is its own weather system, post. Open X, realize it is too long, trim it, post. Same thought, four tabs, four slightly different versions, and by the fourth one the sentence he actually liked had been sanded down into corporate gravel.

That is the tax cross-posting removes. You write the update once, in the InterlinedList box, and it fans out to every network you have connected. This is a Subscriber feature, and I am going to be straight about that up front because it is the first paid thing in this series: cross-posting, along with images, video, and scheduling, lives behind the subscription. On the free plan those toggles are visible but grayed out, and if you try to force a cross-post through the API you get a clean 403 that says "Subscribe to unlock images, video, cross-posting, and scheduled posts." Everything in the first four posts stays free. This is the line.

Connect the accounts once

Before a post can go anywhere, you link the destinations. Each network gets connected through its own OAuth flow in settings, and once connected it is stored as a linked identity on your account. Bluesky, Mastodon (any instance, and you can link more than one), LinkedIn, and X/Twitter are the four.

LinkedIn is the fussy one, and it earns its own paragraph because the targets are richer: you can post as your personal profile, or to organization pages you help run, or to a personal company page. You pick a default target and the composer respects it. The other three are simpler: connect the account, and a toggle for it appears in the composer.

The integrations settings screen showing Bluesky, Mastodon, LinkedIn, and X each with a Connected status

Connect each network once in settings. After that it is just a toggle on the box.

Then it is a set of checkboxes

With accounts linked, the composer grows a settings area (the little cog, which is the part free users see grayed out). Open it and every connected network is a toggle. Want this post on Bluesky and Mastodon but not LinkedIn? Turn two on, leave one off. It is per post, every time, so you are never locked into a fixed broadcast list. The quiet technical note gets one destination; the launch announcement gets all four.

You write your text, flick the toggles for where it should go, and post. Behind the scenes the app publishes to each selected network right then and stores the resulting URLs back on your message, so your one InterlinedList post becomes the hub that knows where all its copies live. If a network hiccups or an account's token has expired, that one fails on its own and tells you, without taking down the post or the others. The post still exists here; the failed network just did not get its copy.

Why the hub model matters

The thing I did not expect to like this much is that the InterlinedList post stays the canonical one. It is not a fire-and-forget blast that scatters four orphaned copies across the internet. Your message here remembers its cross-posted children. That has downstream consequences that show up later in the series: when someone pushes your post, the push can mirror natively as a repost or boost on the networks the original went out to, and when you reply to something that was cross-posted, the reply can follow it out. The hub knows the map.

For the creator, though, the payoff is the boring, daily one. He writes the update in the box he was already using as a notebook. He checks the networks he wants. He hits post once. The sentence he liked goes out intact, four places, in the time it used to take to switch tabs. The copy-paste tax is gone.

There is one thing I glossed over that is about to bite him, and it is a good bite. His favorite updates run long, and X caps out at 280 characters while Mastodon allows 500 and Bluesky sits at 300. So what happens to a 600-character thought when it hits a 280-character wall? That is the next post: limits, automatic threading, and hanging images and video on the whole thing.

Adron