-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cookie Layering Working Session #4
Comments
We realize now that "Comments" is misleading and we plan to change this to "Instructions for Meeting planners." With that in mind, can we move your comment to the description so that potential attendees will see it when we push to the TPAC site and calendar? |
Note I took the liberty to do it, as tooling was losing itself, looking for an "Instructions for meeting planners" section that did not exist. |
Great, no problem, thanks both! |
@johannhof, do you have a link to minutes for this session? Thanks! |
Hey @ianbjacobs, hope all is well! We collectively drafted the start of some of the algorithms we think need to end up in Fetch and in the Cookie RFC: https://gist.github.com/annevk/b6784a10dab2d1c0684f253f225603b0. @johannhof and I plan to continue working on that and hopefully by next TPAC we can show some meaningful progress on this rather old problem. I'm not aware of anyone taking minutes. |
Thanks, @annevk. Looking forward to learning more about this! |
Session description
Following up on last year's breakout session on cookies we want to start hacking on cookie layering and make it more concrete.
We're aiming for a focused working session, not a presentation or large group discussion.
Post-TPAC note: No minutes were taken at this session. Participants collectively drafted some of the algorithms that could end up in Fetch and in the Cookie RFC.
Session goal
Produce tentative modifications to Fetch and Cookies
Additional session chairs (Optional)
@annevk
IRC channel (Optional)
#cookies
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
No response
Estimated number of in-person attendees
Fewer than 20 people
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)
The text was updated successfully, but these errors were encountered: