The time on an entry is yours

Every journal entry records when it was published, in Korean time. A small script in each page shows that time in your time zone instead. If it cannot, you still see the original.

The date under a title looks like the simplest thing on a page. Ours has a little more behind it. The figures here were checked on 12 November 2026, in the script, its tests and the generated pages.

One time, written once

Each entry stores its publish time with an offset, for example 10:50 on 10 November with +09:00, which means Korean Standard Time. That is the time we actually pressed publish, and it is the same text for every visitor, in every language.

A script that converts it

The script is 1,639 bytes and sits inside the page, so it needs no extra request. It finds each marked time, asks the browser for the time zone of your device, and writes the same moment in that zone, in the language of the page: month, day, hours and minutes, and a zone name. Korean and Japanese zones are named KST and JST; elsewhere the browser chooses the name. The original text stays in the tooltip.

Same numbers everywhere

Some languages and regions default to other calendars or digits. The script asks for the Gregorian calendar and Latin digits in every language, so a date never changes its meaning from one page to the next.

When it cannot

If scripts are off, or the browser lacks what the script needs, nothing happens and the Korean time stays as written. The script also skips any time that is not a full date and time with an offset, instead of guessing. It works inside a try block, so a failure on one time does not touch the others.

Where it runs

It is on all 228 post pages (19 entries in 12 languages), on the 12 list pages and on the 12 home pages. Seven tests check the file: its shape, its header, a hash that must match the recorded one, its syntax, and how it behaves in different time zones.

What it does not do

The script only reads your device’s time zone to format a time. It sends nothing anywhere and stores nothing. It changes times that are marked as times; it does not reorder entries.

ipe(); // written once, read in your time

One recorded time, converted at the last step, means that the entry stays the same and only the view of it changes.