| Bluesky | X | |
|---|---|---|
| Characters | 300 | 280 |
| Media | optional | optional |
| Hashtags | 1-2 specific hashtags | 1-2 hashtags, zero is fine |
| Links in body | fine | suppress reach |
| Needs platform approval | no | yes |
Bluesky allows 300 characters; X caps at 280. A post written to Bluesky's length gets truncated — usually mid-sentence — unless it is rewritten, not trimmed.
Bluesky: 1-2 specific hashtags. X: 1-2 hashtags, zero is fine. Carrying the tag block across is the single most obvious sign of an automated cross-post.
Links are fine on Bluesky. On X they cut distribution — the link belongs in a reply, not in the post.
You can post to Bluesky today with a credential you generate yourself. X gates posting behind a platform review — see our API approval notes for what that actually takes.
Bluesky is indie and anti-corporate — polished brand voice reads badly. X is one hook and nothing else — opinionated, conversational, over in a breath. Those are different jobs, so the same words cannot do both well — and every algorithm here demotes text that obviously was not written for it. The fix is not to skip cross-posting; it is to send a native version to each network.
curl -X POST https://postwire.io/api/post \
-H "Authorization: Bearer $POSTWIRE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platforms": ["bluesky", "x"],
"text": "Your post",
"per_platform": {
"bluesky": { "text": "The Bluesky version" },
"x": { "text": "The X version" }
}
}'
PostWire's /api/generate writes those per-platform versions for you from a single prompt, respecting
every limit in the table above. From an AI agent it is one MCP tool call.
Other pairs: X to Bluesky · all combinations · which APIs need approval