veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

248
active users

#libretranslate

1 post1 participant0 posts today

Mónica "la que nunca se está en paz" Gómez ahora presenta...

Una nueva instancia de #LibreTranslate que monté hoy. LibreTranslate es un servicio web de traducción basado enteramente en #SoftwareLibre , que no depende de Google ni de ninguna porquería GAFAM para traducir un montón de idiomas. No es muy rápido y las traducciones tampoco son las más notables, pero funciona muy bien y sirve como alternativa libre a Google Translate.

La instancia está orgullosamente montada desde mi Raspberry Pi (la cual muestro en este video: video.hardlimit.com/w/ikLu3NcB) y está hosteada desde mi hogar. Para darle más uso a mi RPi es muy probable que migre acá mi instancia de #SearX desde mi VPS. En todo caso, no les puedo prometer un uptime del 100% dado que la energía eléctrica se va muy a menudo por mi casa, pero sí les aseguro que mantendré el servicio lo más accesible que se pueda 😉.

Pueden acceder a este traductor en: translate.autumn64.xyz

Si en su celular utilizan "Translate You" pueden poner la URL y las traducciones se harán desde allí.

¡Espero que les sea de utilidad! ;)

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

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

@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.

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.

Replied in thread

Ja @aiquez , Uebersetzung Spanisch <-> Deutsch hapert bei allen und #libretranslate hinkt natuerlich der VC Konkurrenz hinter her. Ist aber bereits gut genug um den Output zu recht zu Ruecken.

Hab schon ueberlegt wir sollten Libretarnslate anhauen und ihnen anbieten ihre Uebersetzung zu berichtigen. Wenn sie das wiederum in eine feed back loop einbauen dann gewinnen wir gegen VC in null Komma nix.

btw
hast deine Deutsche Antwort noch nicht umgestellt aud [DE]. Kannste korrigiern.
#fediPower