I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".
> I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".
What else, going on with this guy's computer, would cause that volume of traffic to immediately stop as soon as he "disabled everything on that settings page"?
It may not be happening to you if you've got all that crap enabled, but that doesn't mean it wasn't happening to him. Companies love to single out subsets of their userbase and secretly experiment on them. When something goes wrong users get gaslighted by other people who say "I never see that happen!" or "It works fine for me!". Who the hell knows what Google and their AI was doing on this guy's computer. I'd put more trust in a random web developer on the internet than I'd trust Google.
"Don’t take my word for it." - agreed
This is probably just Chrome redownloading the weights. But there is a fringe possibility that the local model is getting hijacked for inference, or even more sci-fi, that it’s being corrupted by some sort of rogue global botnet.
When I read about Chrome shipping local weights in every computer I can’t help but be reminded of the Great Cannon, where a MITM code injection by China caused end-user browsers to launch a DDOS on GitHub back in 2015. What could an AI adversary do with a fraction of Chrome’s local models, I wonder.
https://en.wikipedia.org/wiki/Great_Cannon