| Both sides previous revisionPrevious revision | |
| provenance:programming:traffic_files [2026/08/14 03:38] – Add the review log (10 accepted findings across three passes), correct the fold's proxy families and every figure downstream of them, refresh the embedded script output. Authored by Claude. karel.kubicek.claude | provenance:programming:traffic_files [2026/08/14 03:42] (current) – Add §10.6, the generic review pass: 15 accepted findings including two internal contradictions the focused passes could not catch; correct §10.5, which had wrongly justified skipping it. Refresh embedded script output. Authored by Claude. karel.kubicek.claude |
|---|
| "recorded a trace of all HTTP requests initiated by the web page (HAR)"; five of its features are HAR features | "recorded a trace of all HTTP requests initiated by the web page (HAR)"; five of its features are HAR features |
| PETS/2019/4-years-of-eu-cookie-law-results-and-lessons-learned | PETS/2019/4-years-of-eu-cookie-law-results-and-lessons-learned |
| "they dump to file the HTTP Archive (HAR) [55], a JSON-formatted … We look at all HTTP responses with Set-Cookie header in the HAR file." Also analyses the httparchive.org corpus — counted in both. | "they dump to file the HTTP Archive (HAR) [55], a JSON-formatted … We look at all HTTP responses with Set-Cookie header in the HAR file." It ALSO analyses the httparchive.org corpus, so it is the one paper that is both instrument and dataset. This map is single-label and it is filed under instrument, so the dataset row of 14 excludes it — the content page says so rather than implying 15. (The earlier comment here claimed it was "counted in both", which the arithmetic disproves: the five verdicts sum to exactly 95.) |
| PETS/2019/oblivious-dns-practical-privacy-for-dns-queries | PETS/2019/oblivious-dns-practical-privacy-for-dns-queries |
| "Chrome webdriver and record HAR files for each browsing session" | "Chrome webdriver and record HAR files for each browsing session" |
| ==== 10.5 What the review layer cost and returned ==== | ==== 10.5 What the review layer cost and returned ==== |
| |
| Ten accepted findings, zero rejected. The three passes disagreed usefully: only the figures pass could have found F3 and F4 (they need the scripts re-run), only the citation pass could have found C2 (it needs the cited paper read), and only the currency pass could have found E1 (it needs today's release notes). **A fourth, generic pass (''fable'', no checklist) was launched after the other three had been applied, and had not returned when this log was first published.** It is reading the page and this provenance page against the "no MDN, no textbook" test, for overstated claims, unmeasured framing sentences, internal contradictions and scope overlap with [[design:archives]] and [[programming:crawler]]. Its findings will be appended here as §10.6 rather than folded silently into the sections above, so that what the first three passes missed stays visible. | Ten accepted findings, zero rejected. The three passes disagreed usefully: only the figures pass could have found F3 and F4 (they need the scripts re-run), only the citation pass could have found C2 (it needs the cited paper read), and only the currency pass could have found E1 (it needs today's release notes). A fourth, **generic** pass (''fable'', no checklist) was run after the other three had been applied — see §10.6. An earlier version of this section justified //not// running it on the grounds that the three focused passes had covered every category one would. That justification was wrong, and §10.6 is the evidence: the generic pass returned fifteen findings, including two the focused passes were structurally unable to catch. |
| | |
| | |
| | ==== 10.6 Generic (''fable'', no checklist) ==== |
| | |
| | Fifteen findings, **all accepted**. Two of them are the reason this pass exists, because no focused pass could have found them: |
| | |
| | ^ # ^ Finding ^ Verdict ^ |
| | | G1 | The opening ''%%<WRAP important>%%'' box said "Measured on a single page load of a local fixture" and then made the ''serverIPAddress'' claim — which §7.2's own output says the fixture **cannot** show, because both sides are loopback. The claim came from the separate remote re-run, which "What We Ran" did not even mention. | **Accepted.** This is the documented failure mode exactly: the body text carried the qualifier and the prominent box dropped it. Box reworded, the bullet now names the remote run, and "What We Ran" now says the mitmproxy script was run twice. | |
| | | G2 | "14 papers analyse the dataset and 32 use the format, and only one paper does both" contradicts the data structure: ''HAR_VERDICT'' is **single-label**, the five verdicts sum to exactly 95, and the fold's own comment claimed the paper was "counted in both". So the paper the box names as a dataset user is excluded from the 14. | **Accepted**, and the sharpest finding of any pass. Neither a figures check (the counts are all correct) nor a citation check (the paper is right) could see it — it needs the tip box read against the fold's data model. Prose corrected to state the single-label rule explicitly; the false comment in ''traffic_fold.mjs'' corrected. | |
| | | G3 | "in our corpus most papers give none of them" heads a six-item checklist of which exactly **one** was measured. | **Accepted.** An unmeasured claim hiding in a section lead. Replaced with the one figure we have. | |
| | | G4 | The limitations bullet "Nothing on this page claims a HAR loses //x%// of anything on real sites" contradicts §Replay, which quotes 13.9% and <0.3% over 8,544 real origins. | **Accepted.** The bullet meant "nothing //from our fixture//"; it now says that, and credits the percentages to Hantke et al. rather than to us. | |
| | | G5 | The "Volume per 1,000 sites" row traces to nothing — every other number on the page traces to a script or a source. | **Accepted.** Kept, but footnoted as an order-of-magnitude planning estimate with the reason it is not a measurement. | |
| | | G6 | The mitmproxy comparison ran on 11.0.2 while the surrounding section recommends 12.2.3, and the page argues elsewhere that mitmproxy's major versions matter — but the disclosure sat only in "What We Ran". | **Accepted.** Version now stated beside the table, with the page's own argument turned on itself. | |
| | | G7 | The published snippet contains ''.catch(() => {})'' — a silent error swallow, in code a newcomer will copy into a crawler, on a page whose whole argument is that inconsistently-recorded failures are the trap. | **Accepted**, and it is a fair hit: the page published the anti-pattern it warns about. The snippet now logs, with a comment saying why. Re-extracted from the page source and re-run; output unchanged. | |
| | | G8 | 514 + 162 ≠ 679. Three papers vanish with no explanation; a careful reader does the subtraction and concludes a number is wrong. | **Accepted.** The three are the residue papers whose only tool names the fold could not identify. Now stated. | |
| | | G9 | "the older ''dvcs.w3.org'' copy several of them point at" — it is **two** of the six. | **Accepted.** | |
| | | G10 | "no substantive commits since" for BrowserMob is a judgement presented as a checked fact; §8.3 records only a 2024-05-30 push, and nobody examined what it contained. | **Accepted.** Weakened to the recorded evidence. | |
| | | G11 | The regex printed on the page was an abbreviated one, not the regex that was run: it lacked the word boundaries, so as printed it would also match //SHARE// and //CHART// and give a different 95. | **Accepted.** The page now describes the sweep in words and points here for the exact, word-boundary-anchored regex. | |
| | | G12 | "budget roughly the raw byte count plus a third" is contradicted by the page's own run output (100.2% inflation), and the 4/3 base64 rule is textbook material the page's own test excludes. | **Accepted.** Now: text embeds ~1:1 (measured), binary costs ~4/3 (not measured here). | |
| | | G13 | NetLog is named in three tables and never given a sentence — leaving the page with no browser-native answer to a below-HTTP question, on a page that warns about silent QUIC downgrades. | **Accepted.** New short section. | |
| | | G14 | §10.5 was now false. | **Accepted** — this section. | |
| | | G15 | "12.7% of capture-tool //mentions//" uses a word the provenance explicitly excludes from the denominator. | **Accepted.** "uses". | |
| | |
| | **What this pass cost and returned.** It ran last, on an already twice-corrected page, and still found the two most structural defects on it. The lesson for the next refresh is the one this log got wrong the first time: the focused passes are good at their categories //and that is the problem// — G1 and G2 are both cases of a claim being individually true everywhere it was checked and false where two sections meet. Run the generic pass. |
| |
| ===== 11. Conventions ===== | ===== 11. Conventions ===== |
