> "players submit their actions so that AI agents—the game masters—can calculate the impact of each move and present new challenges"

In the past, this was necessary to offer end-to-end encryption in web applications. Now, we can use the WebAuthn PRF extension[0] to enable encryption directly from a passkey, without having to deal with awkward key storage[1].

[0]: https://github.com/w3c/webauthn/wiki/Explainer:-PRF-extensio...

[1]: https://confer.to/blog/2025/12/passkey-encryption

Also useful for things like DPoP: https://datatracker.ietf.org/doc/html/rfc9449

Unrelated to the post, but please include a viewport tag[0] on your website; it's one line of code that makes things far easier to read on mobile.

[0]: `<meta content="initial-scale=1,width=device-width" name="viewport">`

I’m curious about that meta viewport declaration and where it came from: I don’t believe I’ve ever seen it in that order. The customary ordering has the attributes and content properties all reversed:

  <meta name="viewport" content="width=device-width,initial-scale=1">

No. You either design the site to be fully responsive (which would necessarily include CSS changes), or leave out that line. If your CSS assumes a desktop layout, it is strictly better not to set the viewport width to device-width so that the mobile browsers will use the traditional desktop viewport and the user can zoom around without anything broken. In contrast, carelessly slapping that line without CSS changes will often lead to content being clipped and invisible on mobile. This is why I have a bookmarklet to delete any viewport meta elements.