That's in the roadmap, yes.

Telemetry can be disabled on: about:addons -> Firefox Translations -> Preferences and then disabling "Report high-level user interaction" and "Report errors"

Telemetry can be disabled on: about:addons -> Firefox Translations -> Preferences and then disabling "Report high-level user interaction" and "Report errors"

Models are downloaded only once and then cached, and not repeatedly like the OP mentioned. Source: Me. I've developed it. If you disagree, are seeing a different behavior or have further questions, please reach out in the repo: github.com/mozilla/firefox-translations/

Thanks once for the response, and eleventy times for actually developing a non-cloud translation thingy. As for the caching thing I was really hoping this was the case so I guess that makes it three.

Good to know! I still hope you can find a better place to host the files, but it's nice knowing the problem only happens once per file (so long as the cache remains anyway)

No usage data is sent to Google. Only the models are stored on GCS under Mozilla's account and tracking is not even an option.

They can still tell the number of downloads, thus the number of users using this when a new language model update is released.

DOM changes should be handled and it should be working still. Could you please file a bug https://github.com/mozilla/firefox-translations/issues with the proper steps to reproduce, please?

Oh! They work now! Hell yeah nice :)

I'm glad to hear.

> The first release translated endless twitter scroll inline perfectly.

This is the right behavior and it's still working for me. Could you please file an issue to: https://github.com/mozilla/firefox-translations/issues with your STRs?

This is definitely not the right behavior. Could you please file an issue with steps to reproduce or mail the team (address is in the addon page)

Thanks, I will do that! It happens for me on all sites in all containers, that's why I thought it was intentional. Thanks!

You are correct, models are downloaded only once and then cached.

You are right in your statement: the models are downloaded only once and cached. If that's not the case for some users, it should be filed as an issue

But what about updates? I assume they need to be updated once in a while?

We retrain models as we get new datasets and only if they improve, which is not common. So far we haven't updated any model. When it's time, then yes, they will be updated, but it's definitely not a frequent process.