This Post Should Be a Thread By Now

remember at the end of building bear flows i said i’d just feed the site’s rss into my social media scheduler and we’d be off to the races? well, we’re off. this post is the race.

the scheduler’s been quietly taking every post here and dropping it on 𝕏 as a single tweet with the og card, which was fine, but a blog post squeezed into one tweet always felt like shouting a headline through a letterbox. so we built thread mode: the daemon reads the full post, carves it into a proper thread, hook tweet up top, the meat in the middle, link back to the blog at the end.

first attempt fell flat on its face, mind. the thread came out as two tweets, which is not a thread, that’s a tweet with a shadow. turned out the daemon was ingesting the rss teaser instead of the full article, so it was building threads out of the first paragraph and nothing else. classic. the fix was making the daemon’s feed path use the same validated extraction the rest of the pipeline uses, which is one of those bugs that’s obvious the moment you find it and invisible for the week before.

here’s the daft bit though: you can’t re-test with an old post. the scheduler keeps a watermark of everything it’s seen, so the only way to prove the fix works end to end is to write something new and let it flow through on its own. which means this post has a job. if you’re reading this as a proper thread on X, three or four tweets deep, then the whole pipeline held: bear note, publish, rss, daemon, thread. if you’re reading a single lonely tweet, well, at least the blog link works.

either way it’s a nice place to be. write in bear, tag it, walk away, and the machinery does the distribution while i get on with the actual building. that was the whole point of all this.