←back to thread

Unpacking Google’s Web Environment Integrity specification

(vivaldi.com)
756 points dagurp | 1 comments | 26 Jul 23 11:30 UTC | HN request time: 0s | source
Show context
Zopieux ◴[26 Jul 23 19:55 UTC] No.36883955[source]▶
As usual, a thousand word essay on Google's WEI without ever mentioning that Apple sailed that ship silently a while ago, therefore not attracting any attention or backlash.

https://httptoolkit.com/blog/apple-private-access-tokens-att...

https://toot.cafe/@pimterry/110775130465014555

The sorry state of tech news / blogs. Regurgitating the same drama without ever looking at the greater picture.

replies(5): >>36884233 #>>36884293 #>>36884650 #>>36885087 #>>36885253 #
bezout ◴[26 Jul 23 20:39 UTC] No.36884650[source]▶
The post states it. This is not a problem because Safari is not the leading web browser. Apple has very limited power over what they can do with it.
replies(2): >>36886091 #>>36886423 #
1. kevincox ◴[26 Jul 23 22:30 UTC] No.36886091[source]▶
Exactly. Websites will not require this version because they know that Safari is a minority market share and they can't force users to buy an Apple product. However if this is supported by Chrome and Safari all of a sudden the equation flips and many sites will feel that they can reject service to other users.