<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web Browsers on MacWorks</title><link>https://macworks.dev/tags/web-browsers/</link><description>Recent content in Web Browsers on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/web-browsers/index.xml" rel="self" type="application/rss+xml"/><item><title>2026-05-05</title><link>https://macworks.dev/docs/archives/hackernews/hackernews-2026-05-05/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/archives/hackernews/hackernews-2026-05-05/</guid><description>&lt;h1 id="hacker-news--2026-05-05"&gt;Hacker News — 2026-05-05&lt;a class="anchor" href="#hacker-news--2026-05-05"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="top-story"&gt;Top Story&lt;a class="anchor" href="#top-story"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The single most explosive thread today is a forensic takedown of Google Chrome silently installing a 4 GB Gemini Nano model on users&amp;rsquo; machines without consent. Beyond the obvious privacy and disk-space outrage, the technical community is digging into the absurdity of the rollout: the highly visible &amp;ldquo;AI Mode&amp;rdquo; in the browser&amp;rsquo;s omnibox still routes queries to the cloud, meaning the 4GB local model is a pre-staged, unrequested resource that costs immense global bandwidth for features hidden behind obscure context menus.&lt;/p&gt;</description></item></channel></rss>