Treating Bluesky as a first-class network
Why we built Bluesky support on day one, not at the end of the roadmap.
Most schedulers we tried added Bluesky as an afterthought, six months after the protocol's growth made it impossible to ignore. We took the opposite bet: Bluesky is in the v1.0 release alongside X and LinkedIn, and the composer treats all three identically.
Why it matters
Bluesky's growth curve in 2025 looked a lot like Twitter's in 2008. Crucially, the AT protocol is open, which means a scheduler that integrates correctly once does not need to keep chasing API changes the way Twitter scheduling historically required.
For us, the practical benefit is simpler: every Unison customer gets one less tab. If your audience is on Bluesky and your schedule is in Unison, you do not need a second tool to publish there.
How the integration works
Bluesky uses app passwords instead of OAuth. Generate one in your Bluesky settings, paste it into Unison, and you are done. The token is encrypted at rest with the same AES-256-GCM treatment as every other credential we hold.
Settings → Channels → Add channel → Bluesky
Handle: you.bsky.social
App password: abcd-efgh-ijkl-mnopWhat is missing
The Bluesky API does not yet return reach numbers, so the analytics dashboard
shows a — instead of a guess. As soon as the public API surfaces it, we
will wire it up.
That is the only meaningful gap. Everything else (posting, threads, replies, quoting) works exactly like any other channel in Unison.