Chrome looks set to ship an LLM Prompt API to the web platform.
-
@marc_eu if not for the fact that Mozilla ships Firefox with AI chatbots despite a majority of people telling them, "don't do that"...this *would* have been a noble cause.
@yokhai
Yeah, but in all fairness, they're focusing on only local LLM's and, more importantly they implemented a AI kill switch that turns every AI functionality off and is enabled (= no AI) by default. -
Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API.
We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent.
Full details: https://github.com/mozilla/standards-positions/issues/1213#issuecomment-4347988313
@firefoxwebdevs Thing is, Google doesn't care what anyone thinks, especially not Mozilla unfortunately because they own the internet with Chrome. And they push shit that entirely benefits them and not the internet as ecosystem.
-
@yokhai
Yeah, but in all fairness, they're focusing on only local LLM's and, more importantly they implemented a AI kill switch that turns every AI functionality off and is enabled (= no AI) by default.@marc_eu @yokhai None of their LLMs are local, what are you talking about?
PS: Link Previews is enabled by default (and is disabled by the kill switch - weird, right?): https://www.quippd.com/writing/2026/01/06/architecting-consent-for-ai-deceptive-patterns-in-firefox-link-previews.html
-
@firefoxwebdevs I'm assuming @Vivaldi will disable the whole thing, yes?
@wcbdata @firefoxwebdevs @Vivaldi We have been disabling Gemini (GLIC) at compile-time for a while (and we needed to redo that recently after the Chromium team removed all the ifdefs). Several others features are disabled by overriding the "Is this feature enabled?" logic, and in this case, AFAICT this particular API depends on a component that is already disabled that way. (Actually disabling the code for most of those features when building would require hundreds of large and small patches, which would be a maintenance nightmare; I just tried that last week.)
-
Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API.
We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent.
Full details: https://github.com/mozilla/standards-positions/issues/1213#issuecomment-4347988313
@firefoxwebdevs w3m and lynx our only hopes.
-
Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API.
We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent.
Full details: https://github.com/mozilla/standards-positions/issues/1213#issuecomment-4347988313
@firefoxwebdevs it is too late to pretend that you care...
-
@wcbdata @firefoxwebdevs @Vivaldi We have been disabling Gemini (GLIC) at compile-time for a while (and we needed to redo that recently after the Chromium team removed all the ifdefs). Several others features are disabled by overriding the "Is this feature enabled?" logic, and in this case, AFAICT this particular API depends on a component that is already disabled that way. (Actually disabling the code for most of those features when building would require hundreds of large and small patches, which would be a maintenance nightmare; I just tried that last week.)
@TechieNotNetie @firefoxwebdevs @Vivaldi Excellent - thank you!
-
@firefoxwebdevs it is too late to pretend that you care...
@rafaelmartins I raised these same concerns in a podcast two years ago, before I joined Mozilla https://offthemainthread.tech/episode/chromes-llm-ai-api-omg/
So if this is pretend, then wow I'm really committing to the bit.
-
@marc_eu @yokhai None of their LLMs are local, what are you talking about?
PS: Link Previews is enabled by default (and is disabled by the kill switch - weird, right?): https://www.quippd.com/writing/2026/01/06/architecting-consent-for-ai-deceptive-patterns-in-firefox-link-previews.html
@yoasif @yokhai
'None' is incorrect.I just did a fresh install of FF. AI is off by default.
FF has local LLM's like for translation. More will follow (can't find the article about that now).
But yes, *as an option* you can also add third-party LLM's (online).
And link previews:
"Optionally, you can also use AI to read the beginning of the page and generate a few bullet points. To prioritize your privacy, the AI works on your device. This means you’ll need at least 3 GB of available RAM to use the optional AI."Keywords: 'optional' and 'local'.
On-device AI models in Firefox | Firefox Help
Learn what on-device AI models are and how you can manage them.
(support.mozilla.org)
Preview webpages in Firefox with link preview | Firefox Help
Learn how to preview links in Firefox, use AI-generated key points and manage link preview settings.
(support.mozilla.org)
-
@yoasif @yokhai
'None' is incorrect.I just did a fresh install of FF. AI is off by default.
FF has local LLM's like for translation. More will follow (can't find the article about that now).
But yes, *as an option* you can also add third-party LLM's (online).
And link previews:
"Optionally, you can also use AI to read the beginning of the page and generate a few bullet points. To prioritize your privacy, the AI works on your device. This means you’ll need at least 3 GB of available RAM to use the optional AI."Keywords: 'optional' and 'local'.
On-device AI models in Firefox | Firefox Help
Learn what on-device AI models are and how you can manage them.
(support.mozilla.org)
Preview webpages in Firefox with link preview | Firefox Help
Learn how to preview links in Firefox, use AI-generated key points and manage link preview settings.
(support.mozilla.org)
-
-
@marc_eu @yokhai You said that Mozilla is focusing on local LLMs, which is obviously not true, and it doesn't even make contextual sense, since none of the local LLMs in Firefox can serve a prompt API, since they don't respond to prompts.
It isn't "agree to disagree" -- your response was to a comment about chatbots that could respond to prompts - unlike the local LLMs that do not.
-
@rafaelmartins I raised these same concerns in a podcast two years ago, before I joined Mozilla https://offthemainthread.tech/episode/chromes-llm-ai-api-omg/
So if this is pretend, then wow I'm really committing to the bit.
@firefoxwebdevs this is a corporate account, not a personal account. of course there are people at mozilla that care about stuff, but either they are a minority, or they are not loud enough. mozilla as a corporation let me down enough times, I trust you guys less than I trust microsoft, google or apple at this point, and my level of confidence on them is very, very low.
-
Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API.
We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent.
Full details: https://github.com/mozilla/standards-positions/issues/1213#issuecomment-4347988313
@firefoxwebdevs I get the interop trouble, but sad that you can only access the local models more and more devices have by shipping an app to the app store