As open web advocates raise concerns over the Web Environment Integrity proposal, a look at a similar Apple system shipped in 2022 to make Captchas unnecessary
Tim Perry / HTTP Toolkit : Twitter: @pimterry . Forums: Hacker News and r/programming Twitter: Tim Perry / @pimterry : Turns out that Web Environment Integrity proposal everybody is getting angry about (imo very legitimately) was effectively already shipped by Apple in Safari last year 😬 https://httptoolkit.com/... Forums: Hacker News : Apple already shipped attestation on the web, and we barely noticed r/programming : Apple already shipped attestation on the web, and we barely noticed
Context & Ripple Effects
The Web Environment Integrity backlash has a precedent most critics missed: Tim Perry documents that Apple effectively shipped an equivalent attestation system in Safari in 2022, aimed at letting sites verify real devices without CAPTCHAs. That reframes the fight — this is not a novel proposal so much as another engine catching up to something already live.
It also extends a familiar arc: Apple previously declined 16 new Web APIs over fingerprinting risks and drew a deep-dive critique of its WebKit monopoly for stripping capabilities from the web. A system that vouches for the client's environment sits squarely in that pattern — privacy framing paired with tighter platform control.
First-order effects
- Sites running Safari's attestation can already serve verified clients without CAPTCHA challenges, and Perry's write-up means WEI opponents must now argue against a mechanism users are actually subject to, not just a spec draft.
- Open web advocates gain concrete evidence for their objections: the proposal under fire at the standards level mirrors deployed behavior, sharpening the case they bring against Chrome adopting it.
Second-order effects
- Other browser engines face a fork — match the attestation capability or watch sites treat them as second-class clients, the same compatibility squeeze created by Safari's slow adoption of popular features.
- Privacy positioning gets harder to read: Apple built its standing by rejecting tracking-friendly APIs, yet ships device attestation, muddying the signal developers and users rely on to judge which platforms guard the open web.
Third-order effects
- If both major engine camps ship attestation, the web's default shifts toward OS-vouched client trust — platform vendors, not site operators, becoming the arbiters of what counts as a legitimate visitor.
- Standards processes become the battleground: whether attestation hardens into standardized infrastructure or gets resisted as gatekeeping will determine who controls access to the open web for the next cycle.
The trend: Web trust is migrating from server-side checks like CAPTCHAs to platform-vouched device attestation, with each major vendor normalizing the mechanism the previous one shipped quietly.