zlacker

They aren't implementing it as a common browser standard

>>acedTr+(OP)
They shipped it in their browser without intending to standardize it? That's even worse! If true.

>>acedTr+(OP)
PATs are a draft standard with participation by companies other than Apple (such as Fastly and Cloudflare and Google): https://www.ietf.org/archive/id/draft-private-access-tokens-...

>>kccqzy+M4
My impression is that Google abandoned this approach.

>>modele+r
Why is it worst? Isn’t the whole point of an open web to be able to have different agents with different capabilities?

>>isodev+Ap
No, it's to have multiple independent implementations of the same standards.

I can't tell if you are joking, what sort of fragmented hell do you want?

>>progbi+hr
It's a feature designed to work on Apple devices that requires Apple-specific hardware. Why would they make it a standard?

>>progbi+hr
Since when have the standards been finalized before the early implementation? Much of the web has been browsers trying things out and seeing if they can convince others to join them (or, in olden times, following MS's lead as with AJAX).

>>isodev+hs
Because web developers might not be incentivized to implement multiple different attestation protocols?

>>howint+so
My impression is that Google is, once again, just slow at execution. They probably do want to integrate PATs together with their Google One VPN product.