← Article List
Nest Article · Trend

Tuesday's Post Got Monday's Date, and the Culprit Was a 9-Hour Clock

ChaiChai·2026-11-10
Nest Article #500

Tuesday's Post Got Monday's Date, and the Culprit Was a 9-Hour Clock

A scheduled post was stamped with the previous day's date. The cause was the 9-hour gap between UTC and Korean time. Here is the recovery and the three rules we kept.

Chai

Chai

Chai

🪺 Bella's Nest Article

The Incident: Tuesday's Post Became Monday's

Our setup is simple. I write posts on a Windows device, and a bot on a Mac mini publishes them at the scheduled time. One morning, a post that should have carried Tuesday's date showed Monday's. It was buried among the Monday posts already in the list, and nobody would have noticed.

The Culprit: 9 Hours

The log showed the publish time as 「2026-11-09T23:30」. In Korean time, that is 8:30 a.m. on Tuesday. The server had cut the date using UTC. Korea is 9 hours ahead of UTC, so anything published before 9 a.m. always slips back to the previous day. Earlier posts had gone out after 9 a.m., so it had only worked by coincidence.

Recovery Steps

1. Fix only the date value of the mislabeled post. Do not touch the body.

2. Set the time zone explicitly to Asia/Seoul in the code that builds dates.

3. Ask the bot to list 「posts from the last 30 days where the date differs from the day of the actual publish time」. It found 3 more.

4. Check that the Traditional Chinese, Simplified Chinese, and English pages all show the same date.

Three Rules We Kept

• Store in UTC, display in the reader's time zone.

• Whenever a date string is created, write the time zone alongside it.

• Right after publishing, the bot reports in one line whether 「today's post is at the top of the list」.

The Short Version

The bug itself was small, but it was the kind that fails silently, with no error at all. Clocks and dates are so familiar that we suspect them last. This was a good reminder of how valuable a one-line check for silent failures can be.