Ben Kelly

See also #156.

There are use cases for dedicated and shared workers in web platform service workers. Custom (de)compression algorithms that are cpu intensive can use dedicated workers to avoid introducing delays in...

The third-party cookie phaseout effort is not currently targeting webview and the flag is not available in webview. The [chromestatus.com entry](https://chromestatus.com/feature/5133113939722240) says: "Third-Party Cookies will be deprecated on Windows, Mac,...

Any opinions? It seems like chrome and firefox are pretty close. We could try to sidebar about it at TPAC.

> Non-200 status codes can be [stored and revalidated](https://httpwg.org/specs/rfc9111.html#response.cacheability), and [are in practice](https://cache-tests.fyi/#status). Please don't deviate from the HTTP caching spec without good reason - reinventing it causes interop issues...

This linked DT is for "Third-Party Embeds and Services", so the 3P origin is the one that must apply and deploy tokens. It will provide 3P cookies to the 3P...

As a 3P embed you can only apply for the deprecation trial for your own origin. You cannot request tokens for other origins, like recaptcha. In regards to recaptcha support,...

Adding a top-level DT token to your 1P site can address breakage in one or more 3Ps embedded on that site, yes.

I believe third-party cookies are already blocked by default in Chrome on ios. The deprecation trial will have no effect in ios.

Since you own both of these domains, its possible related website sets (RWS) and storage access API (SAA) might be a solution. See references to these here: https://developers.google.com/privacy-sandbox/3pcd