Tomokazu Kiyohara

18 commits

TK

Tomokazu Kiyohara

@kiyohara

Commit activity

18 commits in the last 24 hours

longest streak 1 daycurrent 1

464 / 1,000 XP536 XP to wheel

Today

replying to @mathcrln
Like you, I think the current architecture is a good landing spot. But at the same time, what I think is… The act of pressing the translate button means that a user trigger is required. It requires the will to say, "Alright, I'm going to read this post!" I believe there is an…
Translated from Japanese
Translating everything is not an option for now. The inference costs for translations come from my own pocket, so does Tom’s inference. That’s why we chose this route + TTL on cached translations (because storage comes out of @nunomaduro’s pocket, lol)
Agreed, hadn't thought of it that way but you are right! Personnally, loving "cross languages/cross cultures" stuff, seeing something in a language other than mine, especially japanese, chinese, arabic, etc is bound to call my attention even more than something in one of the…
replying to @mathcrln
What we were comparing it to was ambiguous, wasn't it? We were comparing it to an architecture where only the original text is saved, and it's translated and displayed each time the user presses the translate button. If you move the translation processing to the browser or client…
Translated from Japanese
Oh, yes it was indeed confusing, but now that I understand, I completely agree! Personally I think the current strategy makes the most sense. Inherently translation is something that should be stored since it’s likely to always be the same + many users are likely to need it…
replying to @ralfrtl
You can keep translation costs down, right? Storage costs go up, and there will be more language-difference checks and extra loading queries, but translation using an AI model is the most expensive, so this feels like a reasonable compromise. Good sense of balance.
Translated from Japanese
Out of curiosity, how does doing it like that affect storage costs? If anything, it keeps it down by not storing transalations when not needed, no?

That's @kiyohara's first reply.