- From: Tanvi Vyas <tanvi@mozilla.com>
- Date: Tue, 15 Sep 2020 15:42:38 -0700
- To: public-privacycg@w3.org
- Message-ID: <CALC7Gs7o+oSgZ_oVcfm8q=esuK-s6dLVK==6OgciEvyVPwk+eA@mail.gmail.com>
Just a quick reminder that our virtual face to face is tomorrow! You can find all the details here <https://github.com/privacycg/meetings/blob/master/2020/09-virtual/README.md> . On Fri, Sep 11, 2020 at 3:04 PM Tanvi Vyas <tanvi@mozilla.com> wrote: > Hi all, > > Our virtual face to face is next week and we have finalized our agenda > topics. You can find the full details and agenda here > <https://github.com/privacycg/meetings/blob/master/2020/09-virtual/README.md>. > I have also included the info below, though note the link is the source of > truth as we may make small scheduling tweaks along the way. > > We ask that participants come ready to talk about the issues that interest > them. Thank you! > > ~Tanvi > > *When:* > September 16-17, 15:00–19:00 UTC; 08:00-12:00 PDT; 11:00-15:00 EDT. > > *Agenda* > Day 1 (Wed Sept 16; All times are in PDT) > > - 8:00 - 8:15 Introductions > - 8:15 - 9:00 Storage Partitioning > - Clear-Site-Data for partitioned storage can be used for > cross-site tracking > <https://github.com/privacycg/storage-partitioning/issues/11> > - Expose the first party to a partitioned third party > <https://github.com/privacycg/storage-partitioning/issues/14> > - 9:00 - 9:15 Break > - 9:15 - 10:15 Storage Access API > - Make implicit deny and explicit deny indistinguishable > <https://github.com/privacycg/storage-access/issues/60> > - Require reload after granting requestStorageAccess to get at > unpartitioned storage > <https://github.com/privacycg/storage-access/issues/62> > - 10:15 - 10:45 Break > - 10:45 - 11:45 First-Party Sets > - Desirable elements of "UA Policy" > <https://github.com/privacycg/first-party-sets/issues/20> > - "first-party" token > <https://github.com/privacycg/first-party-sets/issues/5> > - 11:45 - 12:00 Close the day > - 12:00 - 12:10 Optional Break > - 12:10 - 1:00 Optional Mixer / Hallway Chat in breakout zoom rooms > > Day 2 (Thur Sept 17; All times are in PDT) > > - 8:00 - 8:30 IsKnown Proposal > <https://github.com/privacycg/proposals/issues/20> > - 8:30 - 9:00 IsLoggedIn Part 1 > - Should we standardize how we expect browsers to use this signal? > <https://github.com/privacycg/is-logged-in/issues/15> > - Support multi-login and multiple user profiles > <https://github.com/privacycg/is-logged-in/issues/21> > - Support "Remember me" functionality > <https://github.com/privacycg/is-logged-in/issues/9> > - Cater for existing logins, a.k.a. upgrade to IsLoggedIn > <https://github.com/privacycg/is-logged-in/issues/18> > - Prevent 1p websites from fingerprinting IsLoggedIn state in 3p > iframes <https://github.com/privacycg/is-logged-in/issues/13> > - 3p access to isLoggedIn > <https://github.com/privacycg/is-logged-in/issues/19> > - Why expose IsLoggedIn state directly? > <https://github.com/privacycg/is-logged-in/issues/14> > - 9:00 - 9:15 Break > - 9:15 - 10:15 IsLoggedIn Part 2 > - See issues linked above > - 10:15 - 10:45 Break > - 10:45 - 11:45 Proposals > - High-level trust signal (requestInstall / requestTrust)? > <https://github.com/privacycg/proposals/issues/21> > - Speculative Request Control > <https://github.com/privacycg/proposals/issues/19> > - Bounce Tracking <https://github.com/privacycg/proposals/issues/6> > - 11:45 - 12:00 Closing Remarks > > > *Logistics:* > > We'll use our regular *Google Doc > <https://docs.google.com/document/d/1DZEhS1UHJ1PKxt5ZwKmn5LZ4bo10UFyNXeLp2dUuzRM/edit#> > for taking minutes*, and we'll use *these Zoom meeting details*: > > - Meeting ID: 769 153 986 > - Zoom native client: https://mozilla.zoom.us/j/769153986 > - Zoom web client: https://zoom.us/wc/join/769153986?pwd=? > - One tap mobile > - +16699009128,,769153986# US (San Jose) > - +16465588656,,769153986# US (New York) > - Find your local number: https://mozilla.zoom.us/u/a68iWilBp > > We will use the #privacycg channel in PING's slack > <https://w3cping.slack.com/> as an informal chat room during the meeting. > Please try to use slack rather than the zoom chat. If you don't have access > to the slack instance, please contact the chairs for access at > group-privacycg-chairs@w3.org. >
Received on Tuesday, 15 September 2020 22:43:04 UTC