@dahukanna I'm not saying there shouldn't be any further granularity, but the current feature has controls for:

* which language to translate from and to which, if any, should be translated at all;
* which website should be translated.

@dahukanna I will not read whatever is on that link because it's hosted on Google.

@dahukanna That's was not the question.

It's not about gathering data to train, or fine tune any model, or improving the model in any way. It's about using the model to make translations for languages that you authorize translations (automatically, or on-demand).

If you know the feature, you'll know that it's not used before the user authorizes it, and it can be controlled with some granularity.

@CyberPunker @firefoxwebdevs it's not true that there's active AI by default on Firefox.

@truh @firefoxwebdevs because accessibility should always be a major native feature.

People who don't like accessibility features being native features, don't have an acceptable argument.

@viralobscurity @firefoxwebdevs this feature doesn't use an LLM... and it's about accessibility, accessibility shouldn't be an optional feature.

@dahukanna @firefoxwebdevs this thread is not about an LLM, or AI-ML feature.

Translations are an accessibility feature, essential for many around the world, this should be a native feature, unless you don' t care about accessibility.

@truh @firefoxwebdevs I generally agree, but I can see exceptions for things such as accessibility features (translation is accessibility), and other features that extend user facing non-ai features and are done with local small models, as long as they are off by default.

@digitalraven @firefoxwebdevs how come a local translation is bs?

@mu @firefoxwebdevs @noah speak for yourself.

@CyberPunker @firefoxwebdevs kill switch doesn't mean opt-out, it means have a single button to disable it.

The thing is that an user might have switched on a couple of AI features, and might have changed its mind, and wanted to disable it all permanently or temporarily, and having a single button to do that is very useful.

@firefoxwebdevs @ohyran keep it off by default as well.

@firefoxwebdevs Just keep in mind to keep all AI features off by default no matter what.

@hex @firefoxwebdevs While I don't want LLM on my browser, some people do... Also, the translations, which is what they are talking about, is not an LLM (as it's pointed on the original toot).

@duke_of_germany @firefoxwebdevs @davidgerard @tante

Other AI features that are not extensions to non-ai features, and are not similar to the language translation feature using a local small model, should definitively be a browser extension.

@duke_of_germany @firefoxwebdevs @davidgerard @tante It depends...
Stuff like the small model they have for language translations, it's ok to be built in, this is a major accessibility feature.

Third party models that are subscription services, or running as self hosted services, but that require user to acquire and configure on the browser for it to work (off by default), can be integrated within the browser, as long as they are extensions to other non-ai browser features.