Looking beyond Prompts for Permissions in Chrome
summary
Chrome shows that shrinking prompts into a tiny chip cuts visible grants from about 20% to 1%, so reduced interruption can also remove desired consent. Chrome deploys automatic permission revocation (revoke after two months of inactivity) and one-time grants (valid only while the tab is open), and ships an on-device Chrome Permission Suggestion Service that predicts refusals and hides prompts for likely denials; heuristics also silence prompts from the worst 10% of notification offenders. These changes ship or are rolling out and shift control from push to user-pull.
AI-written summary · about
chapters (6)
- 0:00Permission prompts in Chrome
- 2:16Problems with prompts
- 5:09Mitigating interruptive prompts
- 9:03Root cause of limitations
- 11:09Rethinking permissions beyond prompts
- 14:21Summary and user-pull model
related talks
11mQuieter notifications permissions
19mExtensions patterns for Manifest V3
01h 19mEffective Transparency and User Controls: Are We Close to a Breakthrough?
41mChrome and the web in 2020
45mWhat’s new in Chrome?
41mhttps://*every site here*
35mEvolving Chrome Extensions with Manifest V3
27mPatterns for privacy
