Bluesky Long-Form vs X Articles vs LinkedIn Newsletter: Which One Wins in 2026?

September 17, 2026 · 11 min read · ThreadGrab

When Bluesky shipped its long-form post format on 2026-05-28, the timing was not accidental. The post explicitly framed itself as a response to X Articles, and TechCrunch's coverage that week made the cross-platform rivalry the lede. Six months later, three long-form products co-exist on the timeline: Bluesky Long-Form, X Articles, and LinkedIn Newsletter. They look similar at first glance — text, headers, an image or two — but they were built for three different audiences and three different business models. Picking the wrong one costs reach; picking the right one compounds.

This guide compares the three on the dimensions that actually decide which one to publish in first: audience, length ceiling, monetization, analytics, and archiva portability. There is no single winner. There is a workflow that fits your specific content, and we walk through how to decide.

The three long-form products at a glance

Bluesky Long-Form: the open-format challenger

Bluesky's long-form post is technically just a post object with a longer text field and a few new embed types for headers, code blocks, and inline media. There is no separate editor — you write inside the same composer you use for a regular Bluesky post, optionally toggle long-form, and publish. The result attaches to the AT Protocol, which means the post has a stable rkey (record key) that any third-party app can read.

The benefit is portability. A post written for Bluesky Long-Form can be:

• Read in any AT Protocol client (Sky Bridge, Flashes, the official Bluesky app)
• Indexed by Graze and Skywatch for search
• Archived as JSON via the app.bsky.actor.post collection
• Syndicated to Mastodon through bridge services like Bridgy Fed

The drawback is reach. Bluesky's user base is still smaller than X's, and the Discover feed (Bluesky's algorithmic timeline) skews toward tech and open-web communities. If your audience is general consumers, you will write into a smaller pond than on X Articles.

Monetization is external. Bluesky does not have an ad-revenue share; long-form authors typically point readers to a Substack, Ghost, or Patreon at the end of the post. This is the same model writers used on Twitter before Revenue Sharing launched, and it works if you have a tight niche audience that follows you off-platform.

How to publish a Bluesky Long-Form post

The composer accepts Markdown-style headers and code fences. Here is a minimal working long-form post as raw JSON for the AT Protocol:

{
  "collection": "app.bsky.actor.post",
  "repo": "did:plc:your-did-here",
  "record": {
    "text": "# Why Bluesky Long-Form matters\n\nLong-form on Bluesky is just a post with extra embed types.\n\n- Markdown headers\n- Code blocks via triple backticks\n- Inline images via embed\n- Up to ~20,000 characters\n\nThe benefit is portability: any AT Protocol client can render it.",
    "createdAt": "2026-09-17T08:00:00.000Z",
    "embed": {
      "$type": "app.bsky.embed.images",
      "images": []
    },
    "facets": [
      {
        "index": { "byteStart": 0, "byteEnd": 33 },
        "features": [{ "$type": "app.bsky.richtext.facet#bold" }]
      }
    ]
  }
}

The facets array is how Bluesky encodes inline formatting without HTML. A facet is a byte range plus a feature type (bold, italic, link, mention, hashtag). The composer builds these for you when you click the B or I buttons, but knowing the shape matters if you script publishes through the API.

X Articles: the ad-revenue incumbent

X Articles launched in 2023 and went through a major rewrite in 2025 that made the editor feel closer to a Medium-style WYSIWYG than a tweet composer. Today, X Articles is the long-form format with the largest built-in audience: any verified account can publish an Article, and X surfaces Articles in For You, in the user's profile, and in search.

The headline feature is X Revenue Sharing. Verified authors earn a share of the ad revenue from impressions on their Articles, paid out through Stripe. The rate is not public, but creators with steady traffic (50,000+ Article impressions per month) report payout rates that compare to Medium's Partner Program in the same period. This is the only one of the three platforms with a native ad-share model.

The trade-off is portability. X Articles live at x.com/<user>/article/<id> and render as a slim HTML page that returns a near-empty body to logged-out clients. Crawlers see a JavaScript shell that hydrates with the article content, which means:

• Google indexes Article URLs but snippet quality is inconsistent
• Archive tools like archive.today and Wayback capture only the shell
• Third-party readers cannot consume X Articles without a logged-in X session

If your priority is reach and revenue on the platform itself, X Articles wins. If your priority is owning the post long-term — say, you want to republish it on your own blog in two years — X Articles is the worst of the three.

How to embed an X Article in your own blog

If you want to reference an X Article from a blog post or a Markdown note, the safest pattern is a quote block with a permalink. Avoid oEmbed scripts — X's oEmbed endpoint is rate-limited and often returns 403 to non-browser user agents:

> **Note from author:** The full thread on X is at
> https://x.com/yourhandle/article/1234567890123456789
>
> I will keep the canonical copy on this blog and post updates
> there. The X version is the secondary copy for reach.

Pair that with a one-line feed of "Updated 2026-09-17: see X Article for the conversation" so readers who land on your blog a year later know which copy is canonical.

LinkedIn Newsletter: the B2B distribution channel

LinkedIn Newsletter is the oldest of the three (2021, opened to all users in 2022) and the most professionally skewed. Every Newsletter publish sends a push notification to every one of your 1st-degree connections, and a digest goes out to subscribers on Wednesdays. Open rates sit between 25 and 35 percent — well above Substack's typical 30-40 percent for cold audiences and far above X's 2-5 percent algorithmic open rate.

The catch is audience composition. LinkedIn's network is gated by professional identity, so the only people who can see your Newsletter are your 1st-degree connections and their networks (if they share it). You cannot reach consumers, hobbyists, or anonymous readers without paid promotion. For B2B consultants, founders, recruiters, and industry analysts, that constraint is a feature: it filters the audience to people with budget and authority.

Monetization on LinkedIn Newsletter is indirect. There is no ad-share and no per-subscriber revenue. What you do get is profile lift: every Newsletter publish drives 5-10x the normal daily profile views, which compounds into inbound leads, speaking invitations, and recruiter outreach. For a B2B consultant charging $300/hour, one viral Newsletter can pay for a quarter.

How to draft a Newsletter that survives LinkedIn's algorithm

LinkedIn suppresses links in the body of a Newsletter — not the cover image link, but inline text links to your own site. The pattern that survives the algorithm is link-in-first-comment-and-cover-image-only:

Cover image: 1200x627 PNG with your headline + your site URL
Headline: max 70 chars, leads with the takeaway
Body: 800-1500 words, no inline links to your own domain
First comment (right after publishing):
  "Full version + references: https://yoursite.com/article-slug"

This is the same pattern LinkedIn influencers use to bypass the link penalty on regular posts, adapted for Newsletter. The Newsletter gets the reach because the link is not in the body; the comment gives the curious reader a path to your site.

Cross-posting workflow: source-of-truth in Markdown

The three formats do not interoperate, but you can write once and publish three times by treating Markdown as the canonical source. The workflow below assumes you author in a .md file and paste into each platform's editor:

# Workflow: one article, three platforms

1. Write canonical copy in /drafts/2026-09-17-foo.md
   - Keep inline links to < 25 per article (Bluesky facet cap)
   - Use triple-backtick code blocks (Bluesky + X both render)
   - Headlines max 70 chars (LinkedIn digest truncation)

2. Publish to Bluesky Long-Form first
   - Paste text into composer, toggle long-form
   - Attach cover image as embed (Bluesky hosts it)
   - Pin the rkey for later archival

3. Publish to X Articles
   - Paste into x.com/compose/articles
   - Re-embed images (X re-encodes; do not cross-link to Bluesky CDN)
   - Wait 5 minutes for indexing, then tweet the URL

4. Publish to LinkedIn Newsletter
   - Paste into Newsletter composer (no inline links to your domain)
   - Set cover image with your site URL baked in
   - Post first-comment link to canonical blog copy

Total time is roughly 25 minutes for a 1,200-word article. The first publish is the highest-leverage: Bluesky because it has the best archival story, then X for reach, then LinkedIn for the B2B tail.

How to archive long-form posts you did not write

Archiving your own work is half the problem. The other half is archiving third-party long-form posts you want to read later, cite, or remix. The portability table at the top of this guide shows the rough ranking, but here is the concrete workflow for each:

# Archive a Bluesky Long-Form post

curl -s "https://public.api.bsky.app/xrpc/app.bsky.feed.getPost?uri=$URI" \
  | jq '.thread.post.record.text' -r > archived.md

# Archive an X Article (logged-in session required)

# Use the x.com API with a valid auth token:
curl -s -H "Authorization: Bearer $X_BEARER" \
  "https://api.x.com/2/articles/$ARTICLE_ID" \
  | jq '.data.text' -r > archived.md

# LinkedIn Newsletter (no public API)
# Best option: print-to-PDF from a logged-in browser session.
# Use SingleFile or Archivebox to capture the rendered DOM.

Bluesky's AT Protocol is the only one of the three with a public, unauthenticated read API. That is the same architectural reason it is the easiest to archive: every post is a public record on a public ledger. X and LinkedIn both treat the post body as a logged-in render, which is why their archiva stories are weaker.

Which one should you publish in first?

Decision rule, by content type:

• Open-web / portable writing (research notes, technical deep dives): Bluesky Long-Form. The AT Protocol gives you a permanent rkey and the post survives even if Bluesky the company pivots.
• Consumer-facing explainer or listicle chasing ad revenue: X Articles. Revenue Sharing pays out, and the For You algorithmic surface still drives more impressions than Bluesky's Discover feed.
• B2B / professional / consulting audience: LinkedIn Newsletter. The 25-35 percent open rate is unbeatable, and the audience is already filtered to people with authority and budget.

For a portfolio writer who cares about longevity, the answer is Bluesky first because the post is portable; for a creator chasing revenue this quarter, the answer is X Articles; for a consultant chasing leads, the answer is LinkedIn Newsletter. There is no shame in publishing to all three — the workflow above takes 25 minutes per article — but the order matters because the first platform indexed becomes the canonical search result.

The Takeaway

The 2026-05-28 Bluesky Long-Form launch turned a two-horse race into a three-horse race, but the three horses are not interchangeable. Bluesky is the open-format challenger with the best archiva story; X Articles is the ad-revenue incumbent with the largest algorithmic reach; LinkedIn Newsletter is the B2B distribution channel with the highest open rate. Pick the one that fits your business model first, then publish to the others in order of archiva portability, not in order of audience size. The post you can still read in 2031 is the post that mattered.