681–690 of 1001 posts
I'm not a fan of this being downloaded by default. Still, I very much prefer that, if something if Chrome uses a LLM, that's done via a local LLM rather than by via an API call
Earlier quoted context omitted.
It’s actually really useful for web devs to have access to a local model. Whether or not browsers should bundle their own rather than using the system-provided model(s) is up for debate, however. For the time being, though, Google does have some of the better small ones. Furthermore, users aren’t going to want to have to wait for an extra thing to download before their web apps can use AI. That’s the thing… Without c…
You haven't even tried to provide a hypothetical example of what a web app should try to do using a local LLM, nor addressed the obvious questions about how that kind of thing should be standardized, what level of local LLM capability is reasonable for a web app to expect, or how permissions for that should be managed given that a local LLM is not just a tax on local storage capacity. So why should anyone take it as…
Pretty sure that ship sailed way back when Flash ruled the Internet, and it's still sailing more than ever today.
Browsers are just weird sandboxed VMs now. They have nothing to do with their original purpose. Don't be mad at me, I like shipping webapps that render documents server-side and use even JS incredibly sparingly. I'm just reporting what I see. The browser exists as a way to make developing completely proprietary apps with proprietary UIs for several platforms cheaper, and Chromium exists to help further that goal including, if necessary, being packaged up and shipped with those apps (Electron).
Earlier quoted context omitted.
You're missing that this is anti-AI activism
We should be actively anti-AI being part of a web browser just like that though.
This article is activism. The re-framing of software that you install intentionally being about breaking your 'consent' is ideological and incendiary. It implies that this is evil. It isn't.
An extra 4GB per user on our NFS home file server is going to be a huge pain (several thousand students). And for our Windows lab machines, they end up in AppData\Local (which isn’t redirected for operational reasons) so we either leave the profiles in place and let them accumulate (suboptimal) or clear out the profiles as we normally do and let it redownload, over and over again. As much as I’m against unexpected 4G…
If Chrome has the #optimization-guide-on-device-model and #prompt-api-for-gemini-nano flags enabled, either because it's part of some Origin Trial / Early Stable Release or something, then web pages will have access to the new Prompt API which allows any webpage to initiate the (one-time) download of the ~2.7 GiB CPU or ~4.0 GiB GPU model using LanguageModel.create() https://developer.chrome.com/docs/ai/prompt-api Wh…
#omnibox-ml-url-scoring-model
#omnibox-on-device-tail-suggestions
#optimization-guide-on-device-model
#text-safety-classifier
#prompt-api-for-gemini-nano
#writer-api-for-gemini-nano
#rewriter-api-for-gemini-nano
#proofreader-api-for-gemini-nano
#summarizer-api-for-gemini-nano
#on-device-model-litert-lm-backend
Then around gemini but not caught by the search for models: #skills (maybe? I think this is implied by "gemini in chrome"?)
edit: I don't see a carte blanch AI disabling option. As much as I dislike Mozilla's growing obsession with AI, at least they give me a top level option to disable all AI stuff. I only keep Chrome around for occasional testing reasons.
I'm not a fan of this being downloaded by default. Still, I very much prefer that, if something if Chrome uses a LLM, that's done via a local LLM rather than by via an API call
I would prefer they use their own electricity to run these LLM that I don't need. Api calls are fine imo, running it on my computer isn't.
Framing this as needing "consent" is deeply misguided. It's as silly as claiming that Microsoft Word installed an English language spellcheck dictionary without your consent. It's just part of the software. You consented to installing the software and having it autoupdate. That covers it. Now we can argue whether or not it's an appropriate amount of disk space or bandwidth to use, but that's just a reasonable practic…
Earlier quoted context omitted.
By that reasoning, any novel/cutting-edge addition to a browser or other software is wrong? Every standard was new at some point.
The question of whether web browsers will one day be expected to normally include an LLM is not at all relevant to the situation at hand, where that absolutely is not the expected or typical behavior of a browser. Google should be asking for consent now even if they expect in several years time to be able to presume consent for this.
An extra 4GB per user on our NFS home file server is going to be a huge pain (several thousand students). And for our Windows lab machines, they end up in AppData\Local (which isn’t redirected for operational reasons) so we either leave the profiles in place and let them accumulate (suboptimal) or clear out the profiles as we normally do and let it redownload, over and over again. As much as I’m against unexpected 4G…
Google should know better. Chrome has local administrator permissions anyway (w/ its updater) so they should have installed a single copy for the entire machine.
It's not cool to give a damn about the people who keep mundane stuff like desktop infrastructure, file servers, etc, working, I guess. The wanton disregard to even talk to a single in-the-trenches corporate sysadmin seems like malice.
Framing this as needing "consent" is deeply misguided. It's as silly as claiming that Microsoft Word installed an English language spellcheck dictionary without your consent. It's just part of the software. You consented to installing the software and having it autoupdate. That covers it. Now we can argue whether or not it's an appropriate amount of disk space or bandwidth to use, but that's just a reasonable practic…
It is changing the product significantly. I wanted/consented to a browser. Nothing more. Agreeable, nothing new with the browser vendor pushing plugins down our throat which are not browser core features, nevertheless not right.