4 ms·
Earlier discussions: Web Environment Integrity API Proposal – https://news.ycombinator.com/item?id=36817305 https://news.ycombinator.com/item?id=36817305 (61
by merricksb 3y ago
Earlier discussions:
Web Environment Integrity API Proposal
– https://news.ycombinator.com/item?id=36817305 https://news.ycombinator.com/item?id=36817305 (618 points/4 days ago/442 comments)
Google Chrome Proposal – Web Environment Integrity – https://news.ycombinator.com/item?id=36778999 https://news.ycombinator.com/item?id=36778999 – (117 points/7 days ago/94 comments)
Web Environment Integrity Explainer – https://news.ycombinator.com/item?id=36785516 https://news.ycombinator.com/item?id=36785516 (87 points/6 days ago/44 comments)
- jvolkman 3y agoAnd related: Apple already shipped attestation on the web, and we barely noticed - https://news.ycombinator.com/item?id=36862494 https://news.ycombinator.com/item?id=36862494 - (530 points/1 day ago/398 comments)
- Brian_K_White 3y agoAs has been pointed out, Apple's captcha-skipper is rather different.
- jsnell 3y agoWhere was that pointed out? To me it seems that they are not all that different on any level[0]. Not in terms of expressed goals, nor in terms of technical capabilities for capacity to exclude minority browsers or operating systems if misused. The only real difference was PATs being launched with a very specific PR spin of "fewer captchas". [0] https://www.snellman.net/blog/archive/2023-07-25-web-integrity-api-vs-private-access-tokens/ https://www.snellman.net/blog/archive/2023-07-25-web-integri...