Added support for status translation with lingva.ml

[retiolus]

An option is missing in the settings to let the user choose his Lingva instance.

[connyduck]

Nice but

• I'd prefer LibreTranslate
• Calling an api and showing the translation in our interface should be the implementation we want. Having the option only on detailed statuses and adding the translation below the original content like Twitter does it maybe.
• we should host a translation service at translate.tusky.app and use it as default instance before making the feature available to users

see also #2188

[thedaviddelta]

Hello everyone, Lingva creator here!

I'm super glad for this work, and super happy that Lingva is being considered for this key task. But I agree with @connyduck about using LibreTranslate.
I created Lingva as a Free as in Freedom front-end for enable people the use of Google Translate engine without loading any propietary Google code in your browser, just like Invidious or Nitter. But if we want to implement any translation service to other Free projects, we should use Free tools, not just front-end substitutes.

For example, by using Lingva here, we would be sending all the translation traffic directly to Google, even if it's using unofficial ways with less tracking, or even if it's completely anonymized because it would travel only between the Lingva and the Google servers.

The LibreTranslate and ArgosTranslate projects are amazing, and they're creating a completely Free translation engine by themselves. I always try to name and support them in case more privacy-aware or FOSS-aware people prefer to use a completely Free engine, even if currently is not as good as the billion-dollar-Google one.

Once again, thanks for the work with this. Translations have been the missing feature for both Mastodon and Tusky for some time. This work will help to bring them closer, using whatever engine we decide to use.
Regards, David.

[connyduck]

we now support them Mastodon translation api