Pages you have already opened now come back without a round trip

Going back to a page you just read no longer waits on the server

The site now keeps the content it has already loaded for five minutes. Clicking back to a project, returning to the blog after reading a post, or moving between topic filters reuses what your browser already has instead of asking the server again. A page you have not opened, or one whose address or filters changed, is still fetched fresh.

The data behind each page is cached the way the page already was

Public page data — the project list, blog posts, changelogs, topics, the temperature, the coding snapshot — is now held at the edge for an hour and refreshed in the background after that. One visitor's read now serves the next visitor, so the database is read once per cache window rather than once per visit. Your browser still checks on every navigation and takes the newer copy as soon as the cache rolls over.

The admin panel is never cached

Editing is deliberately excluded from both layers. Every admin request is marked private and revalidated, and the panel refuses router-cached data, so an edit you have just saved is the edit you see — no stale gallery, no stale form, and nothing from one session served to another.

The status light checks less often

The health indicator now checks once every five minutes instead of every thirty seconds, and pauses while its tab is in the background, probing immediately when you come back. The health endpoint may itself be served from the edge for up to a minute. A tab left open reports an outage at its next check — within five minutes — and a tab you return to reports it as soon as you look at it.

Full technical detail is in the v0.6.4 release notes.