- From: Hadley Beeman <notifications@github.com>
- Date: Tue, 30 Oct 2018 06:43:31 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 30 October 2018 13:43:53 UTC
Just updating this at our [TAG face-to-face in Paris](https://cryptpad.w3ctag.org/code/#/2/code/view/7wU1dtMh-ZlW97EI4Qi98Z62iDVLueV0EgLwp0sHYsA/), since the topic came up in multiple places at TPAC last week. At [WebAppSec's meeting on Tuesday](https://www.w3.org/2018/10/23-webappsec-minutes.html), @wanderview stated that Web Platform WG had wanted a normative private browsing spec to reference when designing their own features. It looks like W3C and WebAppSec are looking at creating a privacy working group. (pinging @wseltzer @mikewest to fill in any gaps there) Also, [PiNG met on Friday](https://www.w3.org/2018/10/26-privacy-minutes.html), and discussed whether private browsing is best addressed with normative specs (which would need a working group. Options include rechartering/expanding WebAppSec or creating that privacy working group) or non-normative notes and requirements, which could be done from an interest group or community group. @samuelweiler and @snyderp were going to investigate those. To all tagged here, please let us know if/how we can help! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/101#issuecomment-434305547
Received on Tuesday, 30 October 2018 13:43:53 UTC