@jerry This seems like a good thread for my security concern.

I noticed a “translate” link on my post. Clicked it to see what would be used. Was disturbed to find that it’s #DeepL. This is a Tor-hostile #Cloudflare site that misleads people into thinking security is taken seriously. Which is the same thing that happends with libretranslate.com.

In principle it’d be most secure to run Argos Translate on the server. But that’s also a heavy process. If translation must be outsourced, I suggest translate.fedilab.app. It’s the same engine as #libretranslate, but without sharing translations with CF.

(edit) guess it’s a good time to republish this:

❌ #GoogleTranslate (#PRISM)
❌ #YandexTranslate [tax(profits) →Putin’s war]
❌ #DeepL (shares sensitive txt w/tech giant; misleads ppl about it)
❌ #LibreTranslate.com (shares sensitive txt w/tech giant; no privacy policy; solicits trust w/buzz phrases “libre”, “free & open”)
🤷 #lingva.ml (FOSS frontend; still Google)
🤷 translate.fedilab.app (no privacy policy but no evidence of mishandling data either)

Running locally:
✅ #ArgosTranslate
✅ #Apertium.org
✅ #translatelocally.com (EU funded)

@Xapajiamnu @mhoye @csgordon retrospective:

https://www.reddit.com/comments/dtppt3/comment/f6y1yq2/

Some of it might be entirely outdated, but I did enjoy gathering the information.

#Firefox #TranslateLocally #BergamotProject #Horizon2020 #EuropeanCommission #multilingual #translation #2019

@Ashki_Faux just found this toot. https://infosec.exchange/@bojkotiMalbona/108271072631878382

There are some other tools I did not know off.

#Apertium
https://apertium.org/
#translatelocally
https://translatelocally.com/