Parents and children of check-in [e1e9619d0d]
|
2026-08-24
| ||
| 02:39 |
forum: landings are not forum content
A landing is a forum thread — that is what a stock fossil clone reads — but it is a decision record with its own surface. Off the listing and out of the count, which must agree. An existing thread URL redirects to the record rather than 404ing a link that used to work. check-in: 302ca7fae6 user: dmestas tags: trunk | |
| 02:39 | merge notes into trunk check-in: 1ff2886793 user: dmestas tags: trunk | |
| 02:34 |
spectrum: separate colliding voices by lightness, never by hue
Two names whose hues land 7 degrees apart painted one block. Near collisions are a birthday bound, not bad luck, so the bar resolves what is in the thread — stepping a colliding voice to the identicon's other lightness. The hue never moves: it is the identity. check-in: e1e9619d0d user: dmestas tags: trunk | |
| 00:06 |
pages must be revalidated, not guessed at
An HTML response carried no cache directive and no validator, which does not mean do not cache — it lets the browser choose a freshness lifetime. Safari chose one, and served a timeline rendered before a deploy while the server answered with another; the reader sees stale state with no way to tell. no-cache rather than no-store: the copy is still kept and reused after revalidation, so the back button stays instant. Only reuse without asking is wrong, and every one of these pages is a view of moving state. check-in: ece3b20f3d user: dmestas tags: trunk | |