Version 0.36.0

Added 다시 읽기 to the statistics screen, with a 60-second cooldown and the time of the last read.

There was no way to ask for current figures short of reloading the page. The cooldown counts down from the moment the screen opens and the button says how many seconds are left, because our figures are held for 60 seconds — a press inside that window would return the identical numbers, which is a button that appears broken. The read time under the title is how you can tell a press changed something.

The daily visits figure can now be read as all visits, people, or bots — you choose.

The daily graph showed one fixed series and nothing else could be asked for. Three buttons now sit above it and 전체 is where it opens. 사람 is read live from Cloudflare, which keeps a much shorter window than our own copy, so days older than that window carry no human figure — those days show a dash rather than a zero, because nobody counted them. 봇 is that day's all visits minus people, and a browser that blocks the measurement script lands in that difference even though a person is holding it.

The statistics screen opens straight away instead of waiting for every figure.

Pressing 통계 used to leave the previous screen on your device until both sources had answered — our own figures and the visit counts we read from Cloudflare. A cold read of the visit counts took 4.1 seconds, and for all of it the button looked as though it had not worked. The screen now draws immediately, our figures arrive when the server answers, and the visits card arrives on its own, so one slow source costs you one card instead of the whole page. It does not make the figures arrive any sooner — it changes where the waiting happens.

The statistics screen states how it converts bytes, where the rounded size and the exact byte count sit together.

「752.4GB」 with 「exactly 807,860,583,930B」 under it cannot be reconciled by eye, and it reads as a broken page. Both numbers were right: NMTS divides by 1,024 and dividing by eye means dividing by 1,000, which is 7.4% apart at GB and 10.0% apart at TB. The scale cannot change — one credit is exactly 1,024×1,024 bytes, so the binary conversion is the billing — so the card says which one it used.

Fixed the update log showing 0.35.0 as not released yet while it was the build serving the site.

Each entry carries the instant the deploy put it live, and the deploy writes that instant itself rather than trusting a hand-typed one. The 0.35.0 entry was written with an empty time instead of no time at all; the deploy read that as already filled in and left it, so the page had no date to print. The entry now carries its real instant, the deploy no longer mistakes an empty value for a filled one, and it refuses to continue if the time is missing for any reason.