Open jeffsikes opened 1 year ago
No place in the server side settings, alas, so this definitely need to be stored locally. Which immediately poses the question how this would be synced between iPhone/iPad/macOS.
As for preventing excessive use of the deepL API: It should be possible to do this translation only if the user has her own deepL API key configured.
Another thought: this might impact scrolling performance pretty much when every post needs to be translated before being displayed.
What if it was only available from the account view of a specific profile instead of within home, local and federated timelines?
I like the idea but I have a few concerns. It could bring high cost for the instance side translation service or my own if it fallback to it. Still listing it in feature requests.
✅ Search that this request doesn't already exist before creating it.
This would require saving user preferences outside of the Mastodon account itself so I figure the answer is going to be no immediately 😅
The idea here is that I follow an account that posts in another language. I always click translate for those posts.
Would love if those posts would auto translate without the extra click! In the same spot where you choose Notify me on new messages, mute this account, etc add a "Always Translate" option.
If there is a cost related to each translation, could it just be associated to the DeepL API integration that each user pays for?