▲ 973 ▼ Google's New Web Environment Integrity Proposal Dismissed by Brave, Mozilla, and Vivaldi (news.itsfoss.com) submitted 3 years ago by nils@feddit.de to c/technology@beehaw.org 106 comments fedilink hide all child comments
[–] shrugal@lemm.ee 39 points 3 years ago (1 child) Apple already added basically the same thing about a year ago: https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/ permalink fedilink source parent hideshow 2 child comments replies: [–] floofloof@lemmy.ca 12 points 3 years ago (1 child) Is this technically equivalent to Google's proposal? Apple say that their version was developed in collaboration with Google, so it would be surprising for Google to go and deploy a second version of the same thing, were it not for the fact that Google always has two competing versions of everything. And I guess the main reason people are more concerned about Google's version is that they are so dominant in the browser market. permalink fedilink source parent hideshow 2 child comments replies: [–] shrugal@lemm.ee 26 points 3 years ago The details are a bit different. PATs use HTTP headers during a request while WEI is a JS browser API. But otherwise the general structure and end result are the same. A website requests an integrity check, an attester checks your device, and if the attester doesn't like your device then you're SOL. permalink fedilink source parent
[–] floofloof@lemmy.ca 12 points 3 years ago (1 child) Is this technically equivalent to Google's proposal? Apple say that their version was developed in collaboration with Google, so it would be surprising for Google to go and deploy a second version of the same thing, were it not for the fact that Google always has two competing versions of everything. And I guess the main reason people are more concerned about Google's version is that they are so dominant in the browser market. permalink fedilink source parent hideshow 2 child comments replies: [–] shrugal@lemm.ee 26 points 3 years ago The details are a bit different. PATs use HTTP headers during a request while WEI is a JS browser API. But otherwise the general structure and end result are the same. A website requests an integrity check, an attester checks your device, and if the attester doesn't like your device then you're SOL. permalink fedilink source parent
[–] shrugal@lemm.ee 26 points 3 years ago The details are a bit different. PATs use HTTP headers during a request while WEI is a JS browser API. But otherwise the general structure and end result are the same. A website requests an integrity check, an attester checks your device, and if the attester doesn't like your device then you're SOL. permalink fedilink source parent