- From: Fredrik Hernqvist <notifications@github.com>
- Date: Fri, 02 Aug 2024 04:55:25 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 2 August 2024 11:55:29 UTC
Hi @martinthomson and @matatk ! Sorry for the slow reply. We have updated the explainer with [the main points about the side channel](https://github.com/WICG/web_audio_playout?tab=readme-ov-file#security-and-privacy-considerations) and a [comparison to the RenderCapacity API](https://github.com/WICG/web_audio_playout?tab=readme-ov-file#comparison-to-webaudio-rendercapacity-api), as requested. @matatk thank you for the pointer to the Compute Pressure API discussion. We looked at the Compute Pressure mitigations, and we think that the [Rate Limitation mitigation](https://www.w3.org/TR/compute-pressure/#rate-limiting-change-notifications) could be applied here, which would mitigate the risk that the (preexisting) glitch based side channel is made worse. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/939#issuecomment-2265196546 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/939/2265196546@github.com>
Received on Friday, 2 August 2024 11:55:29 UTC