https://bugs.kde.org/show_bug.cgi?id=491011
Gena <genalo...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
--- Comment #1 from Gena <genalo...@gmail.com> ---
> But, it's not 100% clear if the Mozhi (by the way, it sounds symbolically on
> the Russian: "brain" ;) ) in turn gather what I send via it to the Google or
> any other translator.
The name pronounced as "moli" :) But Mozhi is much more secure. Instead of
sending your data to an engine from your IP, it receives the IP of the
instance. Consider it's as a proxy. You can even create your own instance if
you worry about the instance being compromised.
> The second issue is in that the new approach works noticeably slower.
Try to choose an instance that is close to you. For me it depends on the
instance.
But the main migration reason was maintainability, security and more engines
support. Online engines often breaks and there is literally zero documentation
of how to use API for free. We usually reverse-engineer the API by inspecting
what browser do with web version. We decided easier to delegate it to the Mozhi
team.
> Yandex translator.
That's unfortunate, yes. Should be fixed on Mozhi side:
https://codeberg.org/aryak/libmozhi/issues/3
I just don't know Go, so I can't contribute.
Regardless autodetection in google, I can't reproduce it. Works for me just
fine.
> Finally, IMHO, the main engine switching in the software is a significant
> cause to change its version.
It will be 3.0, I didn't draft a new release.
Ah, you probably installed it from
https://flathub.org/apps/org.kde.CrowTranslate which is based on unpublished
version. I submitted Flatpak manifest to prepare for the upcoming release, I
didn't expect it to be published. I will contact the team about it.
--
You are receiving this mail because:
You are watching all bug changes.
