←back to thread

Disable AI in Firefox

(flamedfury.com)
197 points speckx | 7 comments | | HN request time: 0.32s | source | bottom
1. mentalgear ◴[] No.45696960[source]
Personally, I do not mind it if it's on-device, especially small specialised models (e.g. overview generation, audio generation, etc) with no internet access.
replies(4): >>45697057 #>>45697145 #>>45697255 #>>45697304 #
2. OneDeuxTriSeiGo ◴[] No.45697057[source]
That was the original intent. They only recently added the "chatbot-y" kind of stuff since the infra is all already there. The main uses were for their translation tools and PDF alt-text generation (which I believe disabling ML will disable as they rely on the on-device transformer tools to do).
replies(1): >>45697521 #
3. Terr_ ◴[] No.45697145[source]
In the long term, on-device won't save us from a biased assistant. It might notice we seem tired and insinuate that we could use Mococoa, all natural beans straight from the upper slopes of Mount Nicaragua.

Or—and this happens—it "summarizes" the same text differently, depending on whether the author's name happens to fit a certain ethnicity.

4. dingnuts ◴[] No.45697255[source]
Modern local models make it pretty easy to imagine a future where this would be useful, but they also make extremely apparent that the future has not arrived.

Maybe in five years they will be useful enough that it would have been worth including these features

5. ◴[] No.45697304[source]
6. ASalazarMX ◴[] No.45697521[source]
I disabled browser.ml.enable and local translation was still working. In my case, that's all I need, but it looks like it still allows on-device transformers.
replies(1): >>45700534 #
7. OneDeuxTriSeiGo ◴[] No.45700534{3}[source]
Oh interesting. All the local stuff for a good while was gated under browser.ml.enable but maybe they've finally freed that stuff.