| Files | Last commit | Last update |
|---|---|---|
Correct docs and the sort label ahead of the next release (#41) A docs audit and QA pass over main (0.4.0 plus #37-#40) turned up a handful of places where the docs and the UI had drifted apart: - CHANGELOG: link issue #35 alongside PR #38 on the TTL-outlier entry, to match how the sibling entries cite their issue. Amend the 80-column entry to cover the Time -> Ping header rename and the matching `--once` column widths and right-aligned TTL, and the error-badge entry to mention that the badge also covers the "not a domain name" label. Drop a stray blank line between two bullets in the released 0.4.0 section. - README: bump the Nix pin example to v0.4.0, the newest tag that exists. - app.rs: `SortMode::label` still said "time" for the latency sort, so the footer disagreed with the column #40 renamed to Ping. Say "ping", and update the README key-binding row to match. No changelog entry of its own: the label ships unreleased, covered by the amended #40 entry. - main.rs: document the `"<fg> on <bg>"` theme form in the long --help, which #40 added but never wrote down. - AGENTS.md: the module map was missing theme.rs, globe.rs and world_data.rs, still described sites.rs as id.server-only (NSID leads since #39) and config.rs as resolvers-only (it owns theme/ecs/view too), and app.rs now owns TableLayout. Verified: cargo fmt --check, clippy -D warnings and 120 tests pass; `--once` prints its table; --help shows the new theme line; and driving the real binary through a PTY shows the footer read "sort: ping" after cycling Ctrl+S twice to the latency mode. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
Fit the table in 80 columns, badge errors, coarsen the countdown (#40) * Fit the table in 80 columns, badge errors, coarsen the countdown Three pieces of design feedback from issue #33, all about reading the table rather than what it says. Width: the columns are now sized in `app.rs` (`TableLayout`) rather than left to ratatui's constraint solver, because which column gives way first is a judgement call worth testing. At 80 columns everything the reporter asked for survives — resolver name, Loc, a full IPv4 address, Ping, TTL, Exp and the start of the answer — by shedding the spelled-out status first: the verdict moves to a glyph in the left margin, where a scan down the edge finds the failures. Numeric columns are right-aligned, and the units the header already implies ("ms", the "s" on a raw TTL) are gone. An IPv6 resolver's address is shown whole when there's room and clipped when there isn't; the alternative is cropping the columns the issue asked us to fit. Wide terminals are unchanged: the same status word, the same answer width, the same map/globe thresholds. Errors: `theme.error` is now a `Paint` — a foreground with an optional background, written "<fg> on <bg>" — defaulting to white on bright red, the reporter's `\033[101m`. Only the marker is filled: the row's glyph and the status word. Error messages, map dots, the propagation gauge and slow ping times take the hue alone, since a background behind a sentence turns the row into a red bar and behind a map dot paints a block over the coastline. Countdown: the Exp column uses `fmt_countdown` — two digits and a unit, 59s → 1m → 59m → 1h → 23h → 1d → 99d, truncating so the reading stays a lower bound. A whole column of seconds ticking out of unison was a distraction with no payoff. The advisory notes ("TTL ≈ 2h23m", "old answers expire in ≤ …") keep `fmt_secs`: those are single figures where the precision is the point, not a column that shimmers. Verified with `--once` and through a PTY at 80x24 and 160x24, plus a config of TEST-NET resolvers to draw real ERR rows (white-on-red badge confirmed in the rendered cell attributes). Demo GIF re-recorded. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Fill in the PR number in the changelog Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
Discover anycast sites via NSID, falling back to id.server probes (#39) Site discovery relied on operator-specific identification queries, so only the six resolvers we had hand-wired reported where they actually answered from. NSID (RFC 5001) is the general form of the same question: an EDNS option sent empty on any query, which the answering node echoes back filled with its own identity string. It needs no per-operator support and works on servers that never implemented `id.server`. `dns::nsid` sends a `. NS` carrier query with an empty NSID option — every recursive resolver has the root NS set cached, and it keeps the probe from leaking the domain being watched. Payloads are opaque per RFC 5001, so printable ASCII is taken as-is and anything else is hex-encoded rather than mangled through lossy UTF-8. `sites::parse_nsid` scans the string's labels left to right for a known airport code, handling the node-number suffix (`yul01`, `CS-YYZ3`) and Quad9's `q<iata><n>` POP form. Requiring a *known* airport is deliberate: many NSID strings are pure infrastructure (`pdns-recursor-58b7c5d77d-bjzkj`), and inventing a location from those would be worse than showing the operator's configured region. `discover` now takes `Option<SiteProbe>` and tries NSID first, so every resolver is probed — including ones the user added in the config file, which carry no probe at all. When NSID names no place the old operator query runs exactly as before, so nothing that already resolved to a site changed. Verified against the live resolver list with `--once`: Lumen `US → →JFK`, CIRA `CA → →YYZ`, DNS4EU `EU/Any → →AMS`, DNS.SB `DE/Any → →KIX`, with Google/Cloudflare/Quad9/OpenDNS/CleanBrowsing/UltraDNS unchanged; the same codes render in the TUI driven through a PTY, and a config-only resolver list now reports `→YUL` and `→JFK` where it previously showed `HQ`. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
Keep the majority answer visible below a height-capped globe (#28) * Keep the majority answer visible below a height-capped globe The globe's height cap reserved a fixed 4 rows for the info box — enough for the legend, not for the majority-answer block. On terminals both wide and tall the globe grew to that cap and the resolved values were clipped out of view. The reserve now follows what the info box will actually render: legend only while idle, plus blank + heading + one row per majority value (capped at four) once a round settles. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Drop changelog entry for a bug that never shipped The clipped majority-answer panel was introduced by the unreleased globe work, so no released version had it and users have nothing to note. Record that exception in the AGENTS.md changelog step. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Raise the majority-value row cap from 4 to 20 Four rows truncated realistic multi-value answers (TXT records, larger round-robin pools) for no good reason: the globe's own size floor already protects it on short terminals, so the reserve can afford the full list far more often. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 4 months ago | |
Correct docs and the sort label ahead of the next release (#41) A docs audit and QA pass over main (0.4.0 plus #37-#40) turned up a handful of places where the docs and the UI had drifted apart: - CHANGELOG: link issue #35 alongside PR #38 on the TTL-outlier entry, to match how the sibling entries cite their issue. Amend the 80-column entry to cover the Time -> Ping header rename and the matching `--once` column widths and right-aligned TTL, and the error-badge entry to mention that the badge also covers the "not a domain name" label. Drop a stray blank line between two bullets in the released 0.4.0 section. - README: bump the Nix pin example to v0.4.0, the newest tag that exists. - app.rs: `SortMode::label` still said "time" for the latency sort, so the footer disagreed with the column #40 renamed to Ping. Say "ping", and update the README key-binding row to match. No changelog entry of its own: the label ships unreleased, covered by the amended #40 entry. - main.rs: document the `"<fg> on <bg>"` theme form in the long --help, which #40 added but never wrote down. - AGENTS.md: the module map was missing theme.rs, globe.rs and world_data.rs, still described sites.rs as id.server-only (NSID leads since #39) and config.rs as resolvers-only (it owns theme/ecs/view too), and app.rs now owns TableLayout. Verified: cargo fmt --check, clippy -D warnings and 120 tests pass; `--once` prints its table; --help shows the new theme line; and driving the real binary through a PTY shows the footer read "sort: ping" after cycling Ctrl+S twice to the latency mode. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
| 4 months ago | ||
Discover anycast sites via NSID, falling back to id.server probes (#39) Site discovery relied on operator-specific identification queries, so only the six resolvers we had hand-wired reported where they actually answered from. NSID (RFC 5001) is the general form of the same question: an EDNS option sent empty on any query, which the answering node echoes back filled with its own identity string. It needs no per-operator support and works on servers that never implemented `id.server`. `dns::nsid` sends a `. NS` carrier query with an empty NSID option — every recursive resolver has the root NS set cached, and it keeps the probe from leaking the domain being watched. Payloads are opaque per RFC 5001, so printable ASCII is taken as-is and anything else is hex-encoded rather than mangled through lossy UTF-8. `sites::parse_nsid` scans the string's labels left to right for a known airport code, handling the node-number suffix (`yul01`, `CS-YYZ3`) and Quad9's `q<iata><n>` POP form. Requiring a *known* airport is deliberate: many NSID strings are pure infrastructure (`pdns-recursor-58b7c5d77d-bjzkj`), and inventing a location from those would be worse than showing the operator's configured region. `discover` now takes `Option<SiteProbe>` and tries NSID first, so every resolver is probed — including ones the user added in the config file, which carry no probe at all. When NSID names no place the old operator query runs exactly as before, so nothing that already resolved to a site changed. Verified against the live resolver list with `--once`: Lumen `US → →JFK`, CIRA `CA → →YYZ`, DNS4EU `EU/Any → →AMS`, DNS.SB `DE/Any → →KIX`, with Google/Cloudflare/Quad9/OpenDNS/CleanBrowsing/UltraDNS unchanged; the same codes render in the TUI driven through a PTY, and a config-only resolver list now reports `→YUL` and `→JFK` where it previously showed `HQ`. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
Fit the table in 80 columns, badge errors, coarsen the countdown (#40) * Fit the table in 80 columns, badge errors, coarsen the countdown Three pieces of design feedback from issue #33, all about reading the table rather than what it says. Width: the columns are now sized in `app.rs` (`TableLayout`) rather than left to ratatui's constraint solver, because which column gives way first is a judgement call worth testing. At 80 columns everything the reporter asked for survives — resolver name, Loc, a full IPv4 address, Ping, TTL, Exp and the start of the answer — by shedding the spelled-out status first: the verdict moves to a glyph in the left margin, where a scan down the edge finds the failures. Numeric columns are right-aligned, and the units the header already implies ("ms", the "s" on a raw TTL) are gone. An IPv6 resolver's address is shown whole when there's room and clipped when there isn't; the alternative is cropping the columns the issue asked us to fit. Wide terminals are unchanged: the same status word, the same answer width, the same map/globe thresholds. Errors: `theme.error` is now a `Paint` — a foreground with an optional background, written "<fg> on <bg>" — defaulting to white on bright red, the reporter's `\033[101m`. Only the marker is filled: the row's glyph and the status word. Error messages, map dots, the propagation gauge and slow ping times take the hue alone, since a background behind a sentence turns the row into a red bar and behind a map dot paints a block over the coastline. Countdown: the Exp column uses `fmt_countdown` — two digits and a unit, 59s → 1m → 59m → 1h → 23h → 1d → 99d, truncating so the reading stays a lower bound. A whole column of seconds ticking out of unison was a distraction with no payoff. The advisory notes ("TTL ≈ 2h23m", "old answers expire in ≤ …") keep `fmt_secs`: those are single figures where the precision is the point, not a column that shimmers. Verified with `--once` and through a PTY at 80x24 and 160x24, plus a config of TEST-NET resolvers to draw real ERR rows (white-on-red badge confirmed in the rendered cell attributes). Demo GIF re-recorded. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Fill in the PR number in the changelog Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
Fit the table in 80 columns, badge errors, coarsen the countdown (#40) * Fit the table in 80 columns, badge errors, coarsen the countdown Three pieces of design feedback from issue #33, all about reading the table rather than what it says. Width: the columns are now sized in `app.rs` (`TableLayout`) rather than left to ratatui's constraint solver, because which column gives way first is a judgement call worth testing. At 80 columns everything the reporter asked for survives — resolver name, Loc, a full IPv4 address, Ping, TTL, Exp and the start of the answer — by shedding the spelled-out status first: the verdict moves to a glyph in the left margin, where a scan down the edge finds the failures. Numeric columns are right-aligned, and the units the header already implies ("ms", the "s" on a raw TTL) are gone. An IPv6 resolver's address is shown whole when there's room and clipped when there isn't; the alternative is cropping the columns the issue asked us to fit. Wide terminals are unchanged: the same status word, the same answer width, the same map/globe thresholds. Errors: `theme.error` is now a `Paint` — a foreground with an optional background, written "<fg> on <bg>" — defaulting to white on bright red, the reporter's `\033[101m`. Only the marker is filled: the row's glyph and the status word. Error messages, map dots, the propagation gauge and slow ping times take the hue alone, since a background behind a sentence turns the row into a red bar and behind a map dot paints a block over the coastline. Countdown: the Exp column uses `fmt_countdown` — two digits and a unit, 59s → 1m → 59m → 1h → 23h → 1d → 99d, truncating so the reading stays a lower bound. A whole column of seconds ticking out of unison was a distraction with no payoff. The advisory notes ("TTL ≈ 2h23m", "old answers expire in ≤ …") keep `fmt_secs`: those are single figures where the precision is the point, not a column that shimmers. Verified with `--once` and through a PTY at 80x24 and 160x24, plus a config of TEST-NET resolvers to draw real ERR rows (white-on-red badge confirmed in the rendered cell attributes). Demo GIF re-recorded. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Fill in the PR number in the changelog Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 3 months ago | |
Add 3D rotating globe view toggled with Ctrl+O (#26) * Add 3D rotating globe view toggled with Ctrl+G Ctrl+G morphs the flat resolver map into a spinning orthographic globe and back. The globe reuses the flat map's canvas coordinate space (degrees, square dot aspect), so a single projection function returns the flat position at t=0, the sphere position at t=1, and interpolates between them — coastline points and resolver dots slide from map to sphere in one 700ms smoothstep transition, reversible mid-flight. The sphere is tilted 15° so the northern resolver clusters stay clear of the limb, spins one revolution per 36s (1°/frame at the existing 100ms tick, which already redraws every iteration), and culls points on the far hemisphere with a cutoff that eases in with the morph so back-side points drop out antipode-first instead of all at once. A faint graticule keeps the rotation readable over open ocean. Coastline data is vendored from ratatui-widgets (MIT) because the WORLD_HIGH_RESOLUTION static behind MapResolution::High is private; using the identical dataset keeps the morph seamless at t=0, where draw_map still uses the built-in Map shape. Verified with cargo fmt/clippy/test (7 new unit tests on projection and morph state) and end-to-end through an expect PTY: Ctrl+G shows the globe title and disc, frames differ across 3s of spin (rotation), Ctrl+G again returns a screen pixel-identical (via pyte replay) to a run that never toggled. Also documents a third expect gotcha found during that verification: Tcl sleep stops draining the PTY and blocks the app on a full buffer. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Switch globe toggle from Ctrl+G to Ctrl+O Ctrl+G is the BEL character and gets intercepted by some terminal setups before the app ever sees it. Ctrl+O passes through cleanly (not a tmux prefix, not a GUI-terminal tab/window binding, and raw mode bypasses shell line editing) — and the O looks like a globe. Verified through the expect PTY: Ctrl+O (\017) toggles to the globe and back, identically to the previous binding. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Make the map/globe view responsive to terminal width The globe now earns its keep on small screens instead of floating inside the flat map's 350-degree-wide canvas: panel_geometry() sizes the panel per frame, lerping between the classic wide flat-map panel and a square braille-dot grid that the globe's disc fills, zooming the canvas bounds in step with the morph (degrees-per-dot kept equal in x and y throughout, so the limb stays circular under every clamp). View selection is a policy (ViewMode): auto picks the globe below 190 body columns and the flat map above, animating the morph on resizes that cross the threshold; the globe panel also appears down to 131 columns, where the flat map previously left the panel hidden. The first frame snaps instead of animating so a narrow launch starts on the globe directly. Ctrl+O still toggles, and now pins the choice so a later resize doesn't override the user. --view auto|map|globe and a top-level `view = "..."` config key force the mode (flag beats config); config::load() now returns Settings carrying both the resolver list and the view preference. Verified with the quality gates (11 new unit tests: geometry endpoints, round-limb invariant under height clamps, degenerate sizes, auto thresholds, pinning, snap-then-animate) and end-to-end through expect PTYs: auto flat at 200 cols, live morph to globe on stty-resize to 170 and back at 200; globe by default at 150-160 cols; no panel at 120; --view map hides the panel below 157 and shows the flat map above; config view=globe honored at 200 cols and overridden by --view map. A pyte render of the 160-col frame confirms the disc fills the panel. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> | 4 months ago |