/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google says Chrome 102 will use machine learning running entirely within the browser to silence unsolicited permission requests from websites before they pop up

Richard Lawler / The Verge :

The Verge Richard Lawler

Context & Ripple Effects

Chrome had already expanded its intervention in intrusive web behavior, from blocking malicious auto-redirects to blocking autoplaying sound by default. The Chrome 102 change extends that browser-level gatekeeping to permission prompts, using a model that runs locally rather than a blanket rule.

Later coverage of Chrome automatically disabling unused site notifications shows Google continuing to treat permissions and notifications as settings that should adapt to user behavior, not merely persist after a one-time approval.

First-order effects

  • Chrome 102 users receive fewer unsolicited permission dialogs because the browser can suppress prompts before a website displays them.
  • Websites that rely on immediate notification, location, camera, or similar permission requests lose a direct chance to obtain consent when Chrome identifies the prompt as unwanted.

Second-order effects

  • Publishers and web-app operators have greater incentive to delay permission requests until users take an action that makes the request intelligible, rather than asking on arrival.
  • Google becomes a more active intermediary in the permission funnel: Chrome's on-device judgment determines which site requests reach users, alongside its existing controls over redirects and autoplay.

Third-order effects

  • If Chrome keeps applying local models to browser interruptions, web permissions move further from a site-controlled prompt mechanism toward a browser-managed attention and consent layer.
  • The pattern establishes a privacy-and-usability model in which Chrome can reduce unwanted web behavior without sending the underlying browsing decision to Google, while concentrating more policy power in the browser.

The trend: Chrome is increasingly using browser-side controls, including local machine learning, to mediate when websites may interrupt users or seek consent.

Discussion

  • @ocdtrekkie @ocdtrekkie on x
    The fact that Chrome is adding an ML model just to suppress the Notifications API really confirms it was a bad idea, and should be removed from web standards. https://techcrunch.com/...
  • @dj_hartman Derk-Jan on x
    Chrome: Blasts Apple for years for not implementing webpush and ‘breaking the web’. Also Chrome: Disables notifications for most sites based on ML, because the free for all became a shtshow... Good luck if you end up caught in that ML model unwillingly. https://techcrunch.com/...
  • @bergmayer John Bergmayer on x
    why browser makers agreed to go along with implementing notifications from websites is beyond me. just drop them, bad feature, bad idea, how did you not see abuse coming, etc https://www.theverge.com/...