Bluesky's Long-Form Move: Open Wins Over Paywalled Posts
Bluesky just made long-form content a protocol feature, not a paid perk. Here's why that matters more for Sri Lankan writers and builders than the X rivalry.
Bluesky long-form content landed this week, and the easy story to tell is "Bluesky is copying X Articles." I think that misses the point entirely. The interesting part isn't that you can now read articles inside Bluesky. It's how you can, and who gets to.
I read the news in TechCrunch's report, Bluesky embraces long-form content to counter X Articles by Sarah Perez. What follows is my own take on what it means for anyone in Sri Lanka who writes, codes, or runs a small project on a near-zero budget.
🔍 What Bluesky actually shipped
In version 1.122, released Thursday (28 May 2026), Bluesky integrated with Standard.site so you can read articles, blog posts, and newsletters written in other apps built on the AT Protocol. Think Leaflet, pckt, and Offprint. Those long-form pieces show up in the feed as dynamic link cards with richer previews instead of a bare URL.
It wasn't the only change in the update:
| Feature | What changed |
|---|---|
| Long-form reading | Articles from Standard.site / AT Proto apps render as enhanced cards |
| GIF picker | Refreshed |
| Photo viewer | Improved |
| Moderation | Expanded account-level labeling |
| iOS | Video upload bug fix |
Key takeaway: Bluesky didn't build a blog editor inside its app. It taught its app to read long-form posts that already live elsewhere on an open protocol. That distinction is the whole story.
💰 The paywall is the real headline
Here's the line from the reporting that I keep coming back to: on X, long-form Articles are restricted to paid subscribers or business accounts. Bluesky's version is open to everyone.
| X Articles | Bluesky long-form | |
|---|---|---|
| Who can publish/share | Paid or business accounts | All users |
| Underlying system | Closed platform | Open AT Protocol |
| Portable across apps | No | Yes, across AT Proto apps |
For scale, the article notes Bluesky has "some 44.5 million registered users" against X's "550 million monthly active users." X is far bigger. But size and openness are different axes, and for a student or freelancer who isn't going to pay a monthly fee just to publish a 1,500-word piece, "open to all" beats "bigger" every time.
If long-form is a paid tier on one network and a free protocol feature on another, the free one quietly becomes the default for people who can't expense a subscription. That's most of us.
🌐 Why "interoperable" is the word that matters
The AT Protocol detail is what separates this from a feature checkbox. Because the long-form content lives on the protocol rather than inside one company's app, the same article can surface across multiple apps built on it. The TechCrunch piece lists a whole cluster of AT Proto projects already in the wild: Leaflet, pckt, Offprint, plus community efforts like Eurosky, Blacksky, and Northsky, and even WordPress in the mix. Bluesky also pointed to this direction earlier: in February 2026, Germ became the first private messaging service to launch directly from the Bluesky app.
What this means in practice:
- You write once, in an app you choose.
- The content is addressable on the protocol, not trapped in one feed.
- Other apps can read and display it without asking permission.
- If one app dies, your content and your audience graph don't die with it.
That last point is the one I'd tattoo on a wall. Anyone who built an audience on a platform that later changed its rules knows the feeling of renting land you thought you owned.
🛠️ What I'd do with this as a Sri Lankan builder
I'm not telling you to drop everything and migrate. I'm saying the cost of experimenting here is basically zero, and that's rare. Here's how I'd approach it:
- Publish where you control the export. Whether it's your own site, a static blog, or an AT Proto app, pick something that lets you take your writing with you.
- Treat the social post and the article as two different jobs. The post is the hook. The article is the substance. Write the hook to fit the platform's character limit, then link out to the long piece. Our character counter has live limit indicators for X, LinkedIn, and SMS if you're tuning that hook.
- Watch the AT Protocol space, not just Bluesky. The interesting builds will be the third-party apps. If you're a developer looking for a side project with a real open spec to target, this ecosystem is wide open.
- Keep your drafts in a portable format. I keep mine in Markdown so they move anywhere. If you need a clean PDF to send a client or a publication, our Markdown to PDF converter does it in the browser with no upload.
For a local developer, the bigger opportunity isn't posting on Bluesky. It's that there's now a maturing open protocol with real users, real apps, and no gatekeeper charging for the privilege of building on it. That's the kind of base layer you can put a weekend project, or a startup, on top of.
What this means for you
If you only take one thing from this: long-form publishing is shifting from a platform privilege to a protocol feature. X charges for it. Bluesky made it free and portable. Whichever network wins the popularity contest, the model that lets your writing outlive any single app is the one worth betting on.
Bottom line: Don't pick a side in the Bluesky-versus-X fight. Pick portability. Write somewhere you can leave, in a format you can move, and let the platforms compete for your content instead of the other way around.
For a writer or builder in Sri Lanka working with a learning budget and a slow connection, that shift is genuinely good news. The barrier to publishing serious long-form work just dropped to zero, and the lock-in dropped with it.
Original source
Bluesky embraces long-form content to counter X Articles