libretranslate leaves a lot more to be desired compared to google translate or DeepL.
another option is https://github.com/OwO-Network/DeepLX which lets you use DeepL without a Key until the limit is reached where it can fall back to an API Key if provided
the thing about libretranslate is that the admin can specify a custom domain.
and at that point it's up to the external server to do the translating (which can proxy it to pretty much anything else, including google translator or the thing you linked), as long as the response matches the expected format.
that way we would avoid breaking tos of the external services within this project by simply implementing the libretranslator protocol.
deplx most likely does break deepl tos, since it is spoofing ios app.
the thing about libretranslate is that the admin can specify a custom domain.
and at that point it's up to the external server to do the translating (which can proxy it to pretty much anything else, including google translator or the thing you linked), as long as the response matches the expected format.
Even if this sounds good at first this would still require a more intensive change than simply changing the URL used for the existing DeepL translation system as well as also providing much poorer quality.
Cause I generally feel like adding features just to add them when they don't provide good quality is a bad choice and will just lead to more overhead when merging things when not necessary.
Like I said the simplest and best option would be DeepLX cause essentially we wouldn't be providing it with Sharkey people would still need to set it up themself they can just simply change the URL to point towards a hosted instance of DeepLX.
not exactly. deeplx doesn't exactly implement deepl api, so we would also need to switch to POST-ing json instead of form-urlencoded.
can you please test if deepl api accepts json as post body? i can't get a key
On another note I just checked the TOS and they don't state that running stuff like this is against it in fact the only times they mention modifications or third party is whenever they do something from their side or when the customer is suppose to comply by the applicable use law.
In fact it seems like the only reason it spoofs user agent is for a higher limit compared to the browser user agent who has a lower limit.
Sad moment in my opinion it should just to keep consistency might end up recommending just this version https://github.com/ifyour/deeplx-js as it is small and also offers a button to host on a third party platform right away in case people don't want to set it up locally