What's in our Bluesky drafts folder
Half-finished ideas, why we keep them, and how they turn into posts.
Most of what we post on Bluesky didn't start as a finished idea. It started as a half-sentence dropped into a drafts folder days or weeks earlier. Here's an honest look at what's actually sitting in there right now, and how (or whether) it becomes a real post.
The "reply I never sent" pile
Bluesky's feed is conversational — a lot of the best post ideas start as a reply to someone else's post that we typed out and then didn't send, because it felt like it deserved its own post instead of being buried three replies deep in someone else's thread. These sit in drafts until we find the original context worth restating on its own.
Screenshots with no caption yet
A chunk of the folder is just screenshots — of a metric, a weird UI decision, a customer message — saved with zero text, waiting for whichever angle feels sharpest once we sit down to write. The screenshot is easy; figuring out the one sentence that makes it worth posting is the actual work.
Threads that got too long for one post
Bluesky's per-post character limit means an idea that runs long either gets cut down or turned into a short thread. A few drafts are attempts at the first version that just didn't fit, sitting there until we either trim them ruthlessly or accept it needs three posts instead of one.
Observations about the platform itself
Because Bluesky's audience still skews toward people who think about how social platforms work (moderation, algorithms, decentralization), a good chunk of our drafts are just observations about Bluesky itself — what's different about posting here versus X, what the custom feeds are surfacing, what's changed in the algorithm's behavior lately. These tend to perform well because they're genuinely platform-specific instead of generic social-media advice.
Questions we didn't answer
Sometimes a draft is just a question we asked ourselves and didn't finish thinking through: "why did that post do better here than on X?" These sit until we actually have an answer, at which point they usually turn into a short post or, if there's enough to say, a full blog post like this one.
What actually gets posted
Roughly, drafts fall into three buckets by the time we're done with them: posted as-is, rewritten from scratch keeping only the core idea, or deleted because on a second look it wasn't actually interesting — just something we felt compelled to write down in the moment. That last bucket is the biggest one, and that's fine. A drafts folder isn't a backlog you owe completion to. It's a place to dump half-formed thoughts cheaply so the good ones have a chance to surface later.