The page's footer said "IPv4 only", which was wrong for the page as a whole: each check is a fetch, the browser picks IPv4 or IPv6 for each WAN host, and the local targets are IPv4 addresses. The footer's first line now reads "Latency measured via GET requests | CORS restrictions may affect some measurements"; the rest of the footer and the page are unchanged.
README.md already says this about IPv4 and IPv6, and neither it nor the viewport harness (test/viewport/) quotes the footer text, so neither changes.
TODO.md: this issue moves to the top of Completed Steps, and the layout decision (#30), the top Future Steps item, becomes Next Step. The issue asks to drop a Future Steps item for this; there was none, as it was the Next Step.
Model: opus-5-5
Closes https://git.eeqj.de/sneak/netwatch/issues/111.
The page's footer said "IPv4 only", which was wrong for the page as a whole: each check is a `fetch`, the browser picks IPv4 or IPv6 for each WAN host, and the local targets are IPv4 addresses. The footer's first line now reads "Latency measured via GET requests | CORS restrictions may affect some measurements"; the rest of the footer and the page are unchanged.
`README.md` already says this about IPv4 and IPv6, and neither it nor the viewport harness (`test/viewport/`) quotes the footer text, so neither changes.
`TODO.md`: this issue moves to the top of Completed Steps, and the layout decision (https://git.eeqj.de/sneak/netwatch/issues/30), the top Future Steps item, becomes Next Step. The issue asks to drop a Future Steps item for this; there was none, as it was the Next Step.
Model: opus-5-5
The reason given for the change is not true of every check. TODO.md:26-28, the commit message and the PR body say nothing in the page limits a check to IPv4 and the browser picks IPv4 or IPv6 for each target, but the local targets are IPv4 addresses (src/main.js:165 and src/main.js:174-179), so their checks always use IPv4. Acceptable: all three say it as README.md:200-201 does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses.
Judgement call: the footer change itself is right as it stands; with the WAN hosts free to use IPv6, "IPv4 only" was wrong for the page as a whole, and the issue asks that nothing else in the footer change.
Model: opus-5-5
FAIL (needs-rework).
1. The reason given for the change is not true of every check. `TODO.md:26-28`, the commit message and the PR body say nothing in the page limits a check to IPv4 and the browser picks IPv4 or IPv6 for each target, but the local targets are IPv4 addresses (`src/main.js:165` and `src/main.js:174-179`), so their checks always use IPv4. Acceptable: all three say it as `README.md:200-201` does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses.
Judgement call: the footer change itself is right as it stands; with the WAN hosts free to use IPv6, "IPv4 only" was wrong for the page as a whole, and the issue asks that nothing else in the footer change.
Model: opus-5-5
Each check is a fetch: the browser picks IPv4 or IPv6 for each WAN
host, and the local targets are IPv4 addresses, so "IPv4 only" was
wrong for the page as a whole. The footer's first line drops it and
its separator; the rest of the footer is unchanged. TODO.md moves this
to Completed Steps and the layout decision from Future Steps into Next
Step.
Model: opus-5-5
The TODO.md entry, the commit message and the PR body now say, as README.md does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses; no code changed.
Model: opus-5-5
The `TODO.md` entry, the commit message and the PR body now say, as `README.md` does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses; no code changed.
Model: opus-5-5
PASS: the footer no longer says "IPv4 only" and nothing else in it changed, and TODO.md, the commit message and the PR body now say, as README.md does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses.
Model: opus-5-5
PASS: the footer no longer says "IPv4 only" and nothing else in it changed, and `TODO.md`, the commit message and the PR body now say, as `README.md` does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #111.
The page's footer said "IPv4 only", which was wrong for the page as a whole: each check is a
fetch, the browser picks IPv4 or IPv6 for each WAN host, and the local targets are IPv4 addresses. The footer's first line now reads "Latency measured via GET requests | CORS restrictions may affect some measurements"; the rest of the footer and the page are unchanged.README.mdalready says this about IPv4 and IPv6, and neither it nor the viewport harness (test/viewport/) quotes the footer text, so neither changes.TODO.md: this issue moves to the top of Completed Steps, and the layout decision (#30), the top Future Steps item, becomes Next Step. The issue asks to drop a Future Steps item for this; there was none, as it was the Next Step.Model: opus-5-5
FAIL (needs-rework).
TODO.md:26-28, the commit message and the PR body say nothing in the page limits a check to IPv4 and the browser picks IPv4 or IPv6 for each target, but the local targets are IPv4 addresses (src/main.js:165andsrc/main.js:174-179), so their checks always use IPv4. Acceptable: all three say it asREADME.md:200-201does, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses.Judgement call: the footer change itself is right as it stands; with the WAN hosts free to use IPv6, "IPv4 only" was wrong for the page as a whole, and the issue asks that nothing else in the footer change.
Model: opus-5-5
f24222781btoe432850cdfThe
TODO.mdentry, the commit message and the PR body now say, asREADME.mddoes, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses; no code changed.Model: opus-5-5
PASS: the footer no longer says "IPv4 only" and nothing else in it changed, and
TODO.md, the commit message and the PR body now say, asREADME.mddoes, that the browser picks IPv4 or IPv6 for each WAN host and the local targets are IPv4 addresses.Model: opus-5-5