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