Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
beige.party is one of the many independent Mastodon servers you can use to participate in the fediverse.
A home to friendly weirdos. The Grey Gardens of the Fediverse (but beige). Occasionally graphically cacographic. Definitely probably not a cult (though you'll never be 100% sure). Beige-bless 🙏

Administered by:

Server stats:

449
active users

beige.party: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#libretranslate

0 posts0 participants0 posts today
Public
Fedilab Apps

You might know that #Fedilab runs its own translation server (using #LibreTranslate).
But did you know that the app also supports two other translators?

- #Lingva: you won't need extra steps though you can change the default instance.

- #DeepL: A more powerful translator. It's a paid service but you can get 500,000 characters per month for free.

Everything is configurable in settings Have a look to media descriptions).

More about getting a free DeepL api key: support.deepl.com/hc/en-us/art

Screenshot from Settings > Timelines where the Translator option has been tapped. A pop-up display three translators: Fedilab, Lingva and DeepL. DeepL is selected.
Screenshot when Linga is selected. The default instance is displayed. It can be changed by tapping on it.
DeepL is displayed. There are two entries. One to set the API key and another to set if it is the paid or free version.
Public
Ω 🌍 Gus Posey

I'm sorry, but #LibreTranslate isn't doing a good job with Japanese translations. I'm trying to get Google out of my life but selecting the text and translating it with their service means I can see the subtleties of posts in Japanese, especially when they're hilarious or heartbreaking.

(Some great examples here: @padda )

Replied in thread
Public
Jörg 🇩🇪🇬🇧🇪🇺

@onlytina Das Übersetzungstool wird von deiner Instanz gesteuert. Viele Instanzen haben auf #LibreTranslate umgestellt, da das deutlich günstiger im Betrieb ist.
Allerdings finde ich auch, dass die Übersetzung von LibreTranslate totaler Müll ist. Das Tool kommt nichtmal im Ansatz an die Leistung von Deepl.com heran.

Public
Velocirooster adminensis :bc:

I've been experimenting with enabling translation on my instance and since I've seen zero documentation about how to configure LibreTranslate with a purchased api key, I'm going to share my findings here.

Pretty much every guide out there for enabling translation on a Mastodon instance using LibreTranslate assumes that you are going to be setting up the LibreTranslate server yourself. That's admirable, but translation is pretty resource-intensive. When I tested this on my instance, it was taking about 2 seconds to translate a post, and even longer for longer posts. Plus there were some languages that weren't working at all. That was probably on me for not setting up the language packs correctly. Maybe I'll give it another try, but somewhere in the middle of wrestling with the translation server, I realized that I'm here to run a Mastodon instance, not a LibreTranslate instance, so I went and purchased an api key from LibreTranslate for their lower tier of $29 a month (good for 80 translations per minute). Based on the average donations we get each month, that seemed a reasonable cost that we could afford. The trouble was, configuring the instance to use the api key didn't seem to be working at all.

Now if you go to libretranslate.com it lets you play around with the api and shows what the post request and the subsequent response looks like. In the post request and in the api documentation, the endpoint for the translation service is:

libretranslate.com/translate

but if you set LIBRE_TRANSLATE_ENDPOINT to that value in your .env.production file, it won't work. After a bunch of googling and experimentation, I finally went and looked at the pull request for this feature on GitHub. And that's where I saw that in the code for the post request it takes the configured LIBRE_TRANSLATE_ENDPOINT value and then adds the "/translate" at the end of it.

Even though I was sure I had tried this before, I set LIBRE_TRANSLATE_ENDPOINT to:

libretranslate.com

Without the "/translate" on the end. I restarted the web service and cleared the cache and it started working perfectly.

It'd be nice if any of this was actually documented somewhere.

A screen shot of the Mastodon code that handles the post request to the libretranslate endpoint, showing how it adds the "/translate" to the end of the configured endpoint value: def request(text, source_language, target_language) req = Request.new(:post, "#{@base_url}/translate", body: Oj.dump(q: text, source: source_language, target: target_language, format: 'html', api_key: @api_key)) req.add_headers('Content-Type': 'application/json') req end
Screenshot of my libretranslate configuration in the .env.production file: # translation config LIBRE_TRANSLATE_ENDPOINT=https://libretranslate.com LIBRE_TRANSLATE_API_KEY=[Your API Key] In this case you would replace [Your API Key] with an actual API key purchased from libretranslate
#mastoadmins#libretranslate
Public
Andreas Kilgus

Habe mit trivy mal neugierdehalber Container Images überprüft und bin dann doch etwas erstaunt:

ghcr.io/home-assistant/home-assistant:stable (alpine 3.21.0)
Total: 17 (UNKNOWN: 2, LOW: 4, MEDIUM: 7, HIGH: 4, CRITICAL: 0)
Python (python-pkg)
Total: 4 (UNKNOWN: 0, LOW: 1, MEDIUM: 1, HIGH: 1, CRITICAL: 1)
usr/bin/tempio (gobinary)
Total: 4 (UNKNOWN: 0, LOW: 0, MEDIUM: 3, HIGH: 0, CRITICAL: 1)

libretranslate/libretranslate:latest (debian 11.11)
Total: 112 (UNKNOWN: 2, LOW: 78, MEDIUM: 27, HIGH: 3, CRITICAL: 2)
Python (python-pkg)
Total: 9 (UNKNOWN: 0, LOW: 0, MEDIUM: 3, HIGH: 5, CRITICAL: 1)

Für meinen Geschmack dürften die Zahlen in diesen nicht vollkommen exotischen Images gerne etwas niedriger ausfallen. Mag mich jemand aufklären und beruhigen?

trivy.devTrivyTrivy - All-in-one open source security scanner
#trivy#container#homeassistant
Public *
Urtzi Odriozola :toka:

#LibreTranslate aplikazioak interfazean erabiltzen duen hizkuntza detektorea da #LexiLang. Euskarazko 10.000 hitzen zerrenda bat gehitu diot hitzak ausaz @berria egunkariko albisteetatik erauzita.

Proiektuan onartu eta txertatu dute eta Libretranslate beraren bertsio berri bat ere atera dute LexiLang bertsio honekin!

#GoraSoftwareLibrea

github.com/LibreTranslate/Lexi

GitHubRelease 1.0.3 · LibreTranslate/LexiLangWhat's Changed Improve farsi dictionary by @be4zad in #6 Update README.md by @BoFFire in #8 Adding missing kabyle and occitan by @BoFFire in #7 Initial basque dictionary by @urtzai in #9 add missi...
ExploreLive feeds
About