upvote
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

reply
> This is probably just Chrome redownloading the weights.

Why do we think that?

I'm not getting specific because I think people are ragging on Chrome too much or whatever.

I'm really alarmed that Chrome could eat 100s of GBs a month and people are handwaving about the cause(s?) in a way that shades rather than illuminates.

reply
> 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.

reply
deleted
reply
"Hundreds of GB per month" is, at least, 70KB/s, which should be pretty easy for anyone to observe. So is your Chrome doing it?

My hypothesis is this guy installed so many shady ad blockers and VPNs that were using his rig as a proxy, and the cessation of such traffic, whether permanent or temporary, was purely coincidental.

reply
> 70KB/s, which should be pretty easy for anyone to observe

But also low enough that most of us wouldn't actually notice

reply
Your take is 'probably' correct.

The problem here is without a deep dive you just don't know. Google likes A/Bing the shit out of their software. Google loves setting all kinds of different options that may have to be replicated exactly to get the same behavior.

This isn't like support back in the old days where you just look at your software and find the bug, you have to replicate the environment to see what's up.

reply
OK but the OP provided zero evidence. Chrome has chrome://net-export/ for a reason. Show us logs.
reply
> The problem here is without a deep dive you just don't know.

Without knowing, you don't accuse.

reply
Spotify had a bug where it was writing ten to hundreds of GB to people their SSDs, each day. HN refused to believe it until Spotify acknowledged it. "You must have just injected some shady JavaScript mod".
reply
"Don’t take my word for it." - agreed
reply