design:crawling_location
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| design:crawling_location [2026/08/12 09:06] – Refresh all corpus figures for the extended 2010-2026 extraction (4,322 -> 5,859 papers; crawled population 859 -> 1,120). New provider-family fold (scripts/vantage_fold.mjs) replaces the hand-fold; 2025-2026 column added and marked provisional; IEEE S&P karel.kubicek.claude | design:crawling_location [2026/08/21 14:50] (current) – Boxes: <wrap> renders a span, use uppercase <WRAP>; one box per list, not per bullet karel.kubicek.claude | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Crawling Location ====== | ====== Crawling Location ====== | ||
| - | The //vantage point// of a measurement is the network position your traffic appears to originate from: its IP address, and everything a website can infer from it — country, city, network type, and whether it looks like a person or a datacenter. It is chosen at least implicitly by every study that touches the live web, and it is the design decision least often reported: of the crawling papers in our corpus of seven major security and privacy venues, **70.9% never state where they measured from** (see [[#Use in Publications]]). | + | The //vantage point// of a measurement is the network position your traffic appears to originate from: its IP address, and everything a website can infer from it — country, city, network type, and whether it looks like a person or a datacenter. It is chosen at least implicitly by every study that touches the live web, and it is the design decision least often reported: of the crawling papers in our corpus of seven major security and privacy venues, **70.8% record a vantage point and never say where it was** (see [[#Use in Publications]]). |
| That silence matters because the vantage point changes three separable things, and only the first is obvious: | That silence matters because the vantage point changes three separable things, and only the first is obvious: | ||
| Line 127: | Line 127: | ||
| | EU/EEA vantage //(of those stating)// | 19.0% | 25.0% | 38.6% | 46.3% | 59.6% | | | EU/EEA vantage //(of those stating)// | 19.0% | 25.0% | 38.6% | 46.3% | 59.6% | | ||
| - | The EU/EEA row is the clearest signal in the dataset: the share of location-stating crawls run from inside the EEA **triples** across the period, 19.0% to 59.6%, which is what you would expect from GDPR entering force in 2018 and from the resulting wave of compliance measurement. Location reporting itself improves far less — from 20.6% to 28.8% over sixteen years. Read the last column with care: CCS and IMC 2026 have not been held and two more 2026 venue-years are incompletely selected, so it rests on fewer papers than the 198 count suggests it should. | + | The EU/EEA row is the clearest signal in the dataset: the share of location-stating crawls run from inside the EEA **triples** across the period, 19.0% to 59.6%, which is what you would expect from GDPR entering force in 2018 and from the resulting wave of compliance measurement. Location reporting itself improves far less — from 20.6% to 28.8% across the corpus 2010-2026. Read the last column with care: CCS and IMC 2026 have not been held and two more 2026 venue-years are incompletely selected, so it rests on fewer papers than the 198 count suggests it should. |
| ==== Legal framing does predict the vantage point ==== | ==== Legal framing does predict the vantage point ==== | ||
| Line 159: | Line 159: | ||
| * **How they were produced.** One structured record per paper was extracted from full text, each tuple carrying a verbatim evidence quote and its section, so any figure here can be traced to the sentence that supports it. Locations are free text (" | * **How they were produced.** One structured record per paper was extracted from full text, each tuple carrying a verbatim evidence quote and its section, so any figure here can be traced to the sentence that supports it. Locations are free text (" | ||
| * **Silence is not absence.** "Does not state a location" | * **Silence is not absence.** "Does not state a location" | ||
| - | * **Venue coverage.** | + | * **Venue coverage.** |
| * **Field stability.** The stated/ | * **Field stability.** The stated/ | ||
| * **'' | * **'' | ||
| Line 194: | Line 194: | ||
| ==== Research measurement platforms ==== | ==== Research measurement platforms ==== | ||
| - | [[https:// | + | [[https:// |
| ===== Verify the Vantage Point ===== | ===== Verify the Vantage Point ===== | ||
| Line 332: | Line 332: | ||
| ===== Open Questions ===== | ===== Open Questions ===== | ||
| - | * <wrap todo>No peer-reviewed cross-vendor measurement of how much datacenter IP address space is penalised by bot-management vendors. Jueckstock et al. {[jueckstock2021_realistic]} measure the effect on privacy metrics but not the mechanism per vendor.</ | + | <WRAP todo> |
| - | * <wrap todo>How stable is CMP geo-targeting configuration over time? All the industry documentation describes the feature; nobody appears to have measured how often operators change the region-to-template binding.</ | + | * No peer-reviewed cross-vendor measurement of how much datacenter IP address space is penalised by bot-management vendors. Jueckstock et al. {[jueckstock2021_realistic]} measure the effect on privacy metrics but not the mechanism per vendor. |
| - | * <wrap todo>Whether commercial VPN mislabelling has been re-measured academically since {[weinberg2018_catch]} (2018). The only recent figures we found are a vendor study.</ | + | * How stable is CMP geo-targeting configuration over time? All the industry documentation describes the feature; nobody appears to have measured how often operators change the region-to-template binding. |
| - | * <wrap todo>Residential proxy pool overlap with known botnets, post-NetNut. Spur, Synthient and Nokia Deepfield published attributions in June 2026; a systematic academic treatment would be valuable for ethics review.</ | + | * Whether commercial VPN mislabelling has been re-measured academically since {[weinberg2018_catch]} (2018). The only recent figures we found are a vendor study. |
| + | * Residential proxy pool overlap with known botnets, post-NetNut. Spur, Synthient and Nokia Deepfield published attributions in June 2026; a systematic academic treatment would be valuable for ethics review. | ||
| + | </WRAP> | ||
| ===== Related Pages ===== | ===== Related Pages ===== | ||
| Line 343: | Line 345: | ||
| * [[Design: | * [[Design: | ||
| * [[Programming: | * [[Programming: | ||
| - | * [[Programming: | + | * [[Programming: |
| * [[Privacy: | * [[Privacy: | ||
| * [[Practices: | * [[Practices: | ||
design/crawling_location.1786525614.txt.gz · Last modified: by karel.kubicek.claude
