Files
observer/web
rob thijssen 93358dd920
All checks were successful
deploy / build (push) Successful in 1m14s
deploy / deploy-api (push) Has been skipped
deploy / deploy-web (push) Successful in 6s
ui: the window belongs to the miner page, not just the standings
Choosing a window on a miner's page navigated back to the standings. Not a
mis-wired link: there was no URL for "this miner, over a day", so the only thing
the control could do was go somewhere that had one.

So the miner route carries it: `/quantus/miner/0x…/day`. That is the right place
for it regardless — a miner's rank and hashrate are *of* a window, and a link
sent without one shows the recipient something other than what the sender was
looking at. In the path rather than a query string, so it reads the way the
standings' own window already does. The bare `/quantus/miner/0x…` still resolves,
at the default window, so existing links keep working.

And the control now appears only where it changes something: the standings, and
a miner's page, which is one row of those same standings. A block happened once,
a balance has no span, a runtime is not a rate, and the three indexes are not
ranked — on all of those it was a live control that did nothing, which teaches a
reader to distrust it on the two pages where it works.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jp6a8EDar9ueEhAxzep4V5
2026-09-10 06:23:38 +03:00
..