You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dc0790f
Browse filesBrowse the repository at this point in the historyBrowse files
Keep the readout across refreshes, roll the history window daily, and add keyboard access
Refreshes that bring the same answer leave the cards alone, and a redraw
restores the day being read and the keyboard focus. The 30-day window is
worked out at each render in UTC days, so a tab left open moves to the
new day's shared read and drops the old watcher. Each sparkline is a
focusable slider: arrow keys, Page Up/Down, Home and End read one day,
with the same readout as the pointer and an aria-valuetext.
Copy file name to clipboardExpand all lines: live-dashboard/README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ team's connection.
11
11
| File | What it does |
12
12
| --- | --- |
13
13
|`sf.jsonc`| Declares the `rates` role: one `team` connection, two read tools, pinned arguments, and a 15-minute cache |
14
-
|`index.html`| Imports `/__spacefast/client.js`, watches both tools every 60 seconds, and renders each state the route answers |
14
+
|`index.html`| Imports `/__spacefast/client.js`, watches both tools every 60 seconds, and renders each state the route answers. Each sparkline reads one day by pointer or by keyboard (focus it, then use the arrow keys, Home and End)|
15
15
|`styles.css`| Light and dark styles |
16
16
17
17
The data comes from [Frankfurter](https://frankfurter.dev), a free, open-source
@@ -60,7 +60,9 @@ sf connectors public-serving set rates --enable
60
60
connector answers `connector_tool_not_allowed`.
61
61
-**One shared read.** Every viewer asking the same question in the same
62
62
15 minutes shares one upstream request (`cache: "15m"`). The 60-second
63
-
refresh on the page only checks that shared answer. When the answer came
63
+
refresh on the page only checks that shared answer. The 30-day window is
64
+
worked out at each refresh in UTC days, so a tab left open overnight moves to
65
+
the new day's window and keeps sharing it with new visitors. When the answer came
64
66
from that shared read, the footer shows when it was fetched upstream
65
67
(`cachedAt`); otherwise it shows when the page received it.
66
68
-**Real states.** Before anything is connected, the route answers a state
0 commit comments