A Khosra Demo

Readings from a rain gauge on a roof

Menu

Read After Dark

Some pieces want an hour rather than a date. This one is readable between 11pm and 4am — the reader’s own local time, not the site’s — and shows a notice otherwise.

The gate is in the browser because it can only be there. A server never learns which timezone a reader is in: no request header carries one, so a page served at 2am in Dhaka and 2pm in Toronto is the same bytes (khosra ADR-0237). Deciding by the reader’s clock is therefore the browser’s job, which is the layer test answering the question rather than a preference.

It is also the one thing ADR-0080’s antifeature list allows. That list refuses client-side rendering where the server can do it — and here it cannot. The script arrives only because this page’s own frontmatter names a file beside it, so no other page on this site gains a byte of JavaScript from it.

Waiting for the hour. This piece wants to be read between 11pm and 4am, by your own clock — come back then for the full effect. If you would rather not wait, or your browser runs no JavaScript, read it anyway; it is only better in the dark.

What this is not. It is a ritual, not a lock, and the notice says so out loud: the link is there for anyone without JavaScript, and for anyone impatient. A gate that leaves a reader stuck with no way through is a broken page, not an atmospheric one — and since enforcement is impossible anyway, the honest version asks rather than prevents. The only clock that matters belongs to the person reading.

What a feed carries. A feed reader runs no script, so the hour means nothing there — it would get the waiting notice and a link, which is this page’s machinery and not the piece. So the page shares only its lead, network.share: lead: its feed entry, and the copy a fediverse bridge reads, are the paragraph above the === and a “Continue reading” link here (khosra ADR-0582).

khosra · khata f417e573 · content 7c489ae1 · 228 publications, 4256671 bytes · built in 1.469531857s