Appearance
Bluesky integration
The Bluesky integration publishes through the AT Protocol using an app password rather than your account password. Three hundred characters is a hard limit, so the generated variant is written to fit rather than trimmed to fit.
What the Bluesky integration supports
| Capability | Status |
|---|---|
| Text post | Yes |
| Text length | Up to 300 characters, enforced before publishing |
| Link validation | Yes. A link that does not resolve fails the publish instead of going out broken |
| Scheduled publishing | Yes |
| Approval gate | Yes |
| Images | Not yet, on the roadmap |
| Video | Not yet |
| Polls | No |
What the Bluesky integration can be used for
Bluesky can be used for reaching an audience that left the larger networks, without adding a manual posting step.
Bluesky can be used for link distribution that does not go out broken, because the URL in the post is checked before it publishes.
Bluesky can be used for high-frequency short-form posting at a cost of zero extra editorial effort.
Bluesky can be used as a low-risk place to test a headline before the same idea goes out on the channels that matter more.
Bluesky combined with other integrations
| Combination | What it gives you |
|---|---|
| Bluesky + content pipeline | A 300 character variant per article, generated, not truncated |
| Bluesky + first-party tracker | Whether the channel sends traffic worth the slot in the queue |
| Bluesky + LinkedIn | The same idea in two very different registers, from one approval |
What you need to connect Bluesky
- A Bluesky handle
- An app password generated in Bluesky settings. Never the account password
Frequently asked
Can it post video or images? Not yet. Text posts with links today.
Does it use my real password? No. An app password, which you can revoke at any time without changing your login.