Bluesky Integration

How it works

Connect your Bluesky account to Ferryman using an app password. Once connected, any post you create on your origin platform (like X) is automatically synced to Bluesky within minutes — no copy-paste, no separate app to open, no change to how you already write.

Why cross-post to Bluesky

Bluesky has become the de facto destination for tech, journalism, and open-source conversation that used to live on X. Every wave of X turbulence sends another cohort of writers, developers, and academics over — and they tend to stay. If your audience overlaps with any of those communities, being absent on Bluesky is leaving meaningful reach on the table.

The platform's appeal is structural, not just demographic. Feeds are chronological by default, with optional algorithmic feeds you opt into rather than have imposed on you. There are no ads. The underlying AT Protocol is open, so your identity and follow graph are portable. For creators tired of optimizing for an algorithm that moves the goalposts, this is a meaningful shift in posture.

The cost of being present is low: post natively on X (or wherever you already post), and Ferryman keeps your Bluesky audience in the loop automatically. You don't need a content strategy for Bluesky — you need your existing content to also show up there.

What gets synced

• Text posts, including mentions and hashtags
• Images and media attachments (up to 4 per post)
• Alt text on images — preserved from the source platform
• Long posts automatically split into native Bluesky threads when they exceed 300 characters
• Quote posts and link cards
• Videos up to 3 minutes (Creator plan)

Bluesky-specific behavior Ferryman handles

Bluesky isn't just “X with a different logo” — it has its own conventions, limits, and protocol quirks. Ferryman handles each so your cross-posts feel native, not pasted-in:

• Native thread reconstruction. When a source post exceeds 300 characters, Ferryman splits it into a proper Bluesky thread using the AT Protocol reply structure — not numbered “1/n” standalone posts.
• Mention rewriting. Bluesky handles look like @user.bsky.social. Where a mention from your origin platform can be matched to a Bluesky account, Ferryman rewrites it to the correct Bluesky handle.
• Image resizing. Bluesky's 1 MB per-image limit is tight — Ferryman resizes larger images automatically rather than skipping the post.
• Custom PDS support. If you're on your own AT Protocol server instead of bsky.social, Ferryman authenticates against it the same way.
• Skip rules. Add #noferry to any post and it stays on the source platform — useful for X-specific replies that wouldn't make sense out of context on Bluesky.

Use Bluesky as your origin

Prefer posting on Bluesky? Set it as your origin platform and Ferryman will sync your Bluesky posts to X, Threads, Mastodon, and LinkedIn automatically. A growing number of creators do this — they prefer Bluesky's vibe for writing, but don't want to give up the audience they've built elsewhere.

Setup

1. Sign in to Ferryman with your X account
2. Go to Settings and click Connect next to Bluesky
3. Enter your Bluesky handle and an app password (generate one at Settings → App Passwords in Bluesky)
4. Enable cross-posting and select Bluesky as a target (or origin)

Tips for getting traction on Bluesky cross-posts

Cross-posting is the easy part. Getting your Bluesky audience to actually engage is its own thing — the platform's norms differ from X in ways that matter:

• Keep alt text on. Bluesky's culture treats alt text as table-stakes, not optional. Posts without it can get gently called out.
• Hashtags matter less than custom feeds. Discovery on Bluesky happens through custom feeds (community-curated streams subscribed to like RSS), not the hashtag firehose. Posting in a topic relevant to popular feeds is more valuable than stacking tags.
• Replies are first-class. Quote-tweet-equivalent engagement on Bluesky often lives in reply chains. If a cross-post gets a reply, jumping in natively pays off.
• Avoid context-free X content. Reply-to-someone posts that make no sense without the original X conversation are a good candidate for #noferry. Standalone observations cross-post beautifully.
• Long-form does well. Bluesky's 300-character limit is tight, but multi-post threads on substantive topics get read end-to-end more often than they do on X.