[pineconewarrior]

Last I checked, this feature is paywalled behind specific certificate authorities.

Any news on that?

[fooey]

It's a thing only Google wants, so it'll be an interesting flex of their monopoly powers if it goes anywhere

Very similar to what they tried and failed to do with FLOC

I suspect Google is solidly in too many anti-competitive crosshairs around the world to be able to pull anything like this off.

[seelmobile]

I don't work in this space and hadn't heard of it this. A quick search suggests LetsEncrypt and Mozilla are intentionally not implementing support: https://community.letsencrypt.org/t/cansignhttpexchanges/153...

[folkrav]

Google wanting things, (ab)using their position as the most popular browser to get an implementation out there before there is a standard, then getting surprised that others don't want it. FLoC all over again.

[pineconewarrior]

Thank you for the reply, I was kindof expecting that this would play out as such. I am very excited for the future of browsers and web protocols, but some of them are so exclusive and heavy-handed by Google that I worry.

Google needs to continue their developer relations efforts. I think they want to be on the same team as "us", from a technology perspective. Perhaps if only for the sake of adoption.