Local translations?

Is it just as easy to make an extension that runs a local AI translation model? Translation would benefit from having a community continuously updating and tuning local models for languages.

If it was an extension it would be nice if people could fork it with other models. Just like their AI Tab Grouping feature would be much better forked with a deterministic non-AI grouping system.

▲

johnnyanmac 16 hours ago | parent | prev | next [-]

I had a translation extension for a good 2 years before it was built into FF

▲

asadotzler 16 hours ago | parent [-]

You and a few others. Now it's well over 100 million who have it. We didn't make the back button an extension even though we could have. There's good reasons for making some features default and high on that list is "most people would use it and find it valuable for everyday browsing" which well covers web page translation.

	▲	johnnyanmac 14 hours ago \| parent [-]
		I see it as 100 million who didn't care enough to find a translation extension. Which is fine. Most people stay on the same 20 sites, after all (and some of those even have built in translation tools). >We didn't make the back button an extension even though we could have. The back button isn't even a KB of extra data and and I'd put navigation as the primary job of a web browser. I'm not against a built in translator, but it's a strange comparison to a back button. On a slight tangent, I think there's an under talked about boon yo machine translation: it's widely agreedbti be a comoromise and not a source of truth. That wariness has been missing as of late.

▲

ooterness a day ago | parent | prev [-]

Sounds like a great plugin.