The day has arrived. I can finally present you all my new project.
Inspired by NewPipe, Nitter, Invidious or Bibliogram, here comes Lingva, an alternative Front-end for Google Translate.

It's a completely Free and Open Source project, so you can host your own instance. The directions are on the project's README.
You can also make any kind of contribution. Feel free to Pull Request.


@humanetech please do not mention it without mentioning too which is FLOSS. is still better than using Google but keep in mind that Google still has rights on the generated translation and lingva does not circumvent that issue.



Ooh, this is a wonderful project too. Hmm, I think it is best to create a separate "Translation" category in the list. Project is queued for addition, thank you!


@lutindiscret @humanetech @TheDavidDelta Very interesting project. I’ve got one issue however, this project depends on the Argos library for translations. It seems like Argos includes pre-trained translation models, but they do not list under what license their translation models are distributed. Is it safe to assume that their models are also licensed MIT just like their code repository is?

@lutindiscret @humanetech Yep, he's completely right, Lingva is only a scrapper by the moment, for being able to use the biggest translation engine in the world without Google, not a fully featured alternative with custom engine (like Invidious and PeerTube). Give also support and credit to the amazing people behind LibreTranslate who have built an open source engine.

@TheDavidDelta maybe you should add a disclaimer somewhere. I won't waste my time reading Google ToS but I'm pretty sure that Google owns © on the translation but more that that, I would not be surprised if by submitting your text you don't give them rights on it. I mean, if you are a author and put your creation, It might be no longer yours, but Google's © now... People should think twice before doing that...


@lutindiscret @humanetech Don't worry, Lingva doesn't have the functionality to submit a new suggested text by the moment (and I don't think it'd be a functionality to add to a scrapper XD)

@TheDavidDelta you didn't get me. If I write a book and copy-paste it in Lingva and click to get a translation, I'm not sure I still own the rights on the book I've written. Just like when you upload a photo to Facebook, it belongs to Facebook now, it's no longer yours (FB has the right to sell it). I'm not sure Google just do the work for free...

@lutindiscret Ohh, I see, I really don't think that works like that but it's true you always have to care about these services. If I read the GTranslate ToS and it's that creepe I may add some warning. For the moment I think that saying that it's a GTranslate frontend is enough.

@hamid @lutindiscret @TheDavidDelta

Just a #showerthought ..

With #invidious you see that individual server instances threaten to get overburdened. Snopyta, for instance, has a permanent msg "consider a different instance".

For both self-hosted Libretranslate as well as Lingva federation support might be added, where translation requests can be sent to other instances to distribute load..

/ endshowerthought :)

@humanetech @hamid @lutindiscret It's a good idea, but I don't know if it's neither needed nor possible in the actual Lingva. The main instance is hosted on Vercel and they assume all the hosting costs if it isn't used for profit. And trying to redirect trafic without orquestred kubernetes would require to implement some kind of federated protocol just for scrapping the same endpoint at the end.

@humanetech @hamid @lutindiscret I'm starting to work in another distributed project where there are accounts and that would be probably very usefull, but I don't see that working on Lingva.

Inscrivez-vous pour prendre part à la conversation
libre-entreprise Mastodon

Le réseau social de l'avenir : Pas d'annonces, pas de surveillance institutionnelle, conception éthique et décentralisation ! Possédez vos données avec Mastodon !