design:automated_measurements
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| design:automated_measurements [2026/08/27 22:44] – Route DNS to the new Design:DNS page instead of to Security:TLS certificates and Design:IP classification, which answer different questions. Authored by Claude. karel.kubicek.claude | design:automated_measurements [2026/08/28 19:04] (current) – Route the 'existing-dataset analysis' bullet to the new design:existing_datasets page. Authored by Claude karel.kubicek.claude | ||
|---|---|---|---|
| Line 71: | Line 71: | ||
| * **A user study.** [[Design: | * **A user study.** [[Design: | ||
| - | * **An existing-dataset analysis by itself.** Re-analysing Censys, a CT log, AndroZoo, or last year's crawl is empirical work and it is most of the corpus (2,615 papers). It is not running a measurement. The design questions that remain — which snapshot, which query, which join key — belong | + | * **An existing-dataset analysis by itself.** Re-analysing Censys, a CT log, AndroZoo, or last year's crawl is empirical work and it is most of the corpus (2,615 papers). It is not running a measurement. The design questions that remain — which snapshot, which query, which join key — are [[Design: |
| * **A manual audit, a code analysis, or a system paper.** Those are the three larger '' | * **A manual audit, a code analysis, or a system paper.** Those are the three larger '' | ||
| * **A tutorial on HTTP, DNS, or TLS.** Those are specs. This page is which instrument the field uses to observe them. | * **A tutorial on HTTP, DNS, or TLS.** Those are specs. This page is which instrument the field uses to observe them. | ||
design/automated_measurements.1787870688.txt.gz · Last modified: by karel.kubicek.claude
