Patterns for privacy

on YouTube ↗27m

" summary

Chrome documents concrete Privacy Sandbox changes: Schemeful SameSite lands (testable since Chrome 86) and SameSite defaults force HTTPS or require SameSite=None; referrer default becomes strict-origin-when-cross-origin removing path info; User‑Agent shifts to Client Hints with GREASE and high‑entropy values gated by calls. Practical breakages shown: Cloud Run Button losing repo links and 3‑D Secure checkouts losing session cookies, with fixes like per-link referrer policy, explicit config, payload-auth or Post/Redirect/Get. New APIs to try now: Conversion Measurement API (on-device linking, no shared identifier) and Trust Tokens (blind-signed tokens for bot signals) via origin trials.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 0:57Samesite
3. 2:54Refer
4. 11:20Legacy code
5. 16:53Privacy budget
6. 17:28Origin trials
7. 19:39Web dev live session
8. 22:06Example
9. 25:13Wrap up

" related talks

• 16mOpen web standards with Privacy SandboxRowan Merewood · Google I/O 2022
• 31mPrivacy sandboxBarb Smith, Michael Kleber, Rowan Merewood, Kaustubha Govind · Google I/O 2021
• 13mPreparing for a more private webMaud Nalpas · Google I/O 2021
• 42mA Deep Dive Into SameSite Cookies, What They Are and Why They MatterStephen Rees-Carter · NDC Sydney 2020
• 53mThe Future of CookiesAnders Abel · NDC Oslo 2023
• 29mPrivacy SandboxMarshall Vale, Ari Levenfeld · Bitkom Privacy Conference 2021
• 19mWeb Platform SecurityMike West · dotSecurity 2016
• 50mThe Future of CookiesAnders Abel · NDC Security 2024