The whole thing goes back to mid-January. At my wife’s suggestion, I picked up a book called How to Become Independent Through Writing1. She said she hoped it would help with something I’d been wrestling with.
It did—more than I expected.
And that day I made a decision: come what may, I need to keep writing and stacking up words. And I shouldn’t keep them to myself. Even if it’s a little embarrassing, I should put them out into the wider world.
To be fair, the stage had been set for a long time. The only reason nothing happened was that I was both lazy and shy.
From that day on, I did two big things.
First, I went back through my old Facebook posts and made as many as possible public. Anything too personal I left as friends-only. There wasn’t a “make everything public” button, so I did it gradually over time. I think I ended up reorganizing roughly ten years’ worth of posts. Turns out I wrote a lot. It felt like discovering I’m some kind of ambiguous exhibitionist.
Second, I changed my writing routine. I decided daily-life posts would go only to Facebook and Instagram, while anything technical would also go to LinkedIn and WordPress. Facebook and Instagram would be in Korean; LinkedIn and WordPress in English. I considered Threads and X as well, but decided to expand later.
If you’re thinking, “Wait, I don’t see you posting on Instagram,” that’s because I actually created a new account for this purpose. My old one is strictly for idol fandom activities—there was no way I was going to repurpose that.
Even after making that decision, for a while I was living a quiet life with not much technical material worth writing about.
Then in early February, two things hit at once: OpenClaw showed up in the world, and I started using Claude Code to study SDD. And as you can probably tell, I began writing a lot of technical posts. I’ve got a backlog of personal, everyday topics, but I’ve been too busy writing technical stuff to publish them. Now that I’ve separated the channels, I should start paying attention to that side again.
It’s been a little over a month since I committed to posting across multiple platforms, and so far I’m keeping that promise. But honestly, translating the same post and distributing it to four different places isn’t exactly simple. ChatGPT handles the rough translation, which saves a ton of time, but refining it to match my voice is still on me. Plus, each platform has its own quirks and constraints—there are more small details to manage than you’d expect.
At some point I had a thought: couldn’t I offload part of this work to N.I.C.K., my OpenClaw AI assistant?
It seemed feasible for me to handle the original writing and the final review of the translation, and let the AI take care of the rest. Honestly, it didn’t seem like it could be impossible.
There were two major considerations.
First, this isn’t a one-way workflow. It’s a back-and-forth loop where N.I.C.K. and I pass tasks to each other, so I needed a systematic way to manage it.
Second, I needed to know how solid the publishing APIs were for each platform.
After thinking it through and doing some research, I concluded both issues were manageable—pretty much as I’d expected. I’m now building those pieces step by step. I could probably write several posts just about that process, so stay tuned.
Along the way, I learned one unexpected fact: Facebook and Instagram don’t provide an API for publishing posts—at least not for personal accounts. Apparently, that changed after the Facebook–Cambridge Analytica data scandal2.
Facebook Pages, however, can publish posts via API. My guess is they allow it because Pages are typically used for business or public-facing purposes.
Instagram is similar: if you switch to a business profile, API-based uploads are possible—but only for Reels. Seriously?
Three days after making the decision, I went through some setup and launched my Facebook Page3. That’s where things stand now. There’s still a long way to go—at this point, N.I.C.K. can only handle translation and Facebook Pages uploads on my behalf. But I’ll keep building out the pipeline bit by bit. This whole thing feels a lot like CI/CD, actually.
Kirin's Technology Essay 