Measure The Web

User Tools

Site Tools

Trace: • headers • registration
programming:registration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
programming:registration [2026/08/27 13:08] – Apply focused+generic review: split Cookie Hunter 13.7% vs 25,242; Kubicek 25.7% of unique domains; login_diff segment match and aria-label; recaptcha deprecation; no ToS-consensus claim. Authored by Claude karel.kubicek.claudeprogramming:registration [2026/10/08 20:49] (current) – Finish PII leakage collateral: back-links and provenance; Authored by Claude karel.kubicek.claude
Line 38: Line 38:
 | ''automated-login'' | 15 | 1.8% | | ''automated-login'' | 15 | 1.8% |
 | ''sso'' | 0 | — | | ''sso'' | 0 | — |
 +
 +**The 553 ''none'' row is mostly an inference, and some of it is wrong.** A hand audit of the ''none'' labels on a **different and smaller population** — the **145** of the **260 platform-subject papers with a crawl configuration** ([[design:platforms]]), not these 857 web crawls — read each paper's own text rather than the shared ''crawlConfig'' quote and found **119 (82.1%)** where the paper says nothing about its authentication posture either way, **12 (8.3%)** where it states the collection was unauthenticated, **8 (5.5%)** ambiguous, and **6 (4.1%)** **contradicted by the paper's own text** — one of them scored ''none'' while its own ''crawlConfig'' evidence quote reads "we scrape user photographs from Instagram using an alias account". The two populations overlap but are not the same set, so 82.1% and 4.1% do not transfer to the 553; the transferable conclusion is that ''none'' on this field is the extractor's reading of silence far more often than it is a reading of the paper, so **the 553 is an upper bound and the 81 is a lower one**. Per-paper verdicts: [[provenance:design:platforms]].
  
 The 42 + 24 + 15 = 81. Hand-read, they split like this. A paper can do more than one of these; the label is the job that decided whether it belongs on this page. The 42 + 24 + 15 = 81. Hand-read, they split like this. A paper can do more than one of these; the label is the job that decided whether it belongs on this page.
Line 334: Line 336:
  
 A crawl that only //detects// an SSO button has not logged in. Dimova et al. are explicit about that. Do not cite 7.23% as a login rate. A crawl that only //detects// an SSO button has not logged in. Dimova et al. are explicit about that. Do not cite 7.23% as a login rate.
 +
 +The other half of these studies — SSO, MFA and passkey deployment as the //subject//, with the denominators that go with it — is [[Security:Authentication]]. This page keeps them here for the instrument caveat above; that page carries the prevalence question.
  
 ===== Automated registration ===== ===== Automated registration =====
Line 463: Line 467:
  
   * [[Programming:Interaction]] — depth, typing versus ''fill()'', the logged-out default as a coverage problem   * [[Programming:Interaction]] — depth, typing versus ''fill()'', the logged-out default as a coverage problem
 +  * [[Privacy:PII leakage]] — what leaves once the form is filled: canary identities, the encoding search, and the ethics of synthetic PII
   * [[Programming:Stateful Stateless]] — the profile that login writes into   * [[Programming:Stateful Stateless]] — the profile that login writes into
   * [[Privacy:Consent]] — the banner in front of the form   * [[Privacy:Consent]] — the banner in front of the form
programming/registration.1787836125.txt.gz · Last modified: by karel.kubicek.claude