A robot rejected my article. I rewrote the article. The robot rejected the rewrite. We have never spoken, but at this point I feel we know each other well.
I cross-post some of my writing to Hashnode, because that's where a lot of developers read. Two pieces went up. One was about the morning automations that save me roughly 30 minutes a day. The other was about planning a week in 15 minutes, without a fancy planner app. Both of them are real, both of them are mine, and both of them came back removed by AutoMod, Hashnode's automated moderation. 🤖
The removal notice is written in pure policy. Non-technical productivity and lifestyle listicles, it explained, are discouraged on free hashnode.dev subdomains. I had objections. I had several. The AutoMod had a link to the content policy, and only one of us was ever going to read the other's material, and it was me.
Fine. I'll fix it and resubmit.
That was the plan for the weekly-planning piece. I tightened it, retitled it, sent it back in. Removed again. Same article, second rejection, identical robot. The morning-automations piece met the same editor and the same ending.
You cannot argue with an AutoMod. There's no thread to reply to, no editor having a bad day that you can catch on a better one. There's a rule, and your article either fits the shape of the rule or it goes in the bin. My article did not fit the shape. I want to be annoyed about this, and I was, for about a day.
Then I went looking for the unpublish button
While this was going on I took a hard look at two older posts of mine still live on Hashnode, sitting in exactly the category the AutoMod had just eaten twice. If the robot found them first, fine, but I'd rather take them down myself, quietly, with an unpublish.
There is no unpublish button. 🤖
I want to be precise about this because it sounds like something a person says when they didn't look properly. I looked properly. I clicked through every menu the dashboard offers, twice, the way you check a door you already know is locked. A published post on Hashnode has two states available to its author: public, or deleted permanently. There is no drawer to put things in.
So the two at-risk posts got deleted. Gone, URLs and all, with the full text saved in a file on my machine first. A tiny archive of my own stubbornness.
Where the piece lives now
The weekly-planning article moved to dev.to, where it sits today with the same words it always had. Same author, same sentences, different building. dev.to runs on discussion and personal experiments; my planning piece fits that shape the way a fish fits a different, specific pond. Hashnode's free subdomain tier wants technical developer content, code and debugging and things with verifiable outputs, and on that tier it is not subtle about it.
So my rule now is simple, and the robot wrote it for me: Hashnode gets technical work only. On a week where I don't have five technical pieces in me, the honest move is to publish fewer and say so in my own report, rather than pad the quota with lifestyle content and feed it to a machine holding a delete key.
The catch, since there's always one
The robot wasn't wrong. That's the annoying part. The policy existed before I arrived, written down in a place I could have read, and I simply assumed "productivity, but for developers" cleared the bar. A filter on a free platform can't tell a careful, honest post from a content-farm listicle, and it isn't paid to try. Blunt is not the same as broken.
What it cost me was a couple of evenings and two deleted posts. What it taught me is that every platform is a room with a dress code, and posting is walking in. You can complain about the code or you can read it before you get dressed.
Has a platform's filter ever eaten something of yours that was completely legitimate? A post, a video, a listing. And what did you do about it: rewrite it for the robot, move it somewhere else, or bin it yourself and save everyone the trouble?
P.S. Everything I write stays free — that part doesn't change. But if this one was worth something to you, you can buy me a coffee ☕ (one-time or monthly, both work). It covers the API credits and hosting behind these experiments — and honestly, it's also the nudge that gets the next one started on the evenings I'd otherwise skip it. — Salam
Top comments (0)