zlacker

[return to "Unpacking Google’s Web Environment Integrity specification"]
1. dang+iK1[view] [source] 2023-07-26 18:33:49
>>dagurp+(OP)
I think these are the related threads to date—have I missed any?

Google is already pushing WEI into Chromium - >>36876301 - July 2023 (705 comments)

Google engineers want to make ad-blocking (near) impossible - >>36875226 - July 2023 (439 comments)

Google vs. the Open Web - >>36875164 - July 2023 (161 comments)

Apple already shipped attestation on the web, and we barely noticed - >>36862494 - July 2023 (413 comments)

Google’s nightmare “Web Integrity API” wants a DRM gatekeeper for the web - >>36854114 - July 2023 (447 comments)

Web Environment Integrity API Proposal - >>36817305 - July 2023 (437 comments)

Web Environment Integrity Explainer - >>36785516 - July 2023 (44 comments)

Google Chrome Proposal – Web Environment Integrity - >>36778999 - July 2023 (93 comments)

Web Environment Integrity – Google locking down on browsers - >>35864471 - May 2023 (1 comment)

◧◩
2. benatk+eM1[view] [source] 2023-07-26 18:41:13
>>dang+iK1
I had one but it got flagged, ah well:

- “I don't know why this enrages folks so much.” Googler re Chrome anti-feature >>36868888

I think that just meant some users with sufficient karma flagged it, but I was a bit confused because for a while it didn't say "[flagged]" but didn't show up in the first several pages or continue to get upvotes. Is there a delay in saying "[flagged]"?

◧◩◪
3. dang+uT1[view] [source] 2023-07-26 19:08:05
>>benatk+eM1
The [flagged] marker only shows up after flags exceed a certain threshold, but flags can affect a post's ranking before that.
[go to top]