I don't know if this was mentioned before, it is very hard to digest this 670-post thread - but there is a serious missed opportunnity with Kagi Translate. Orion's Kagi translate seems to be based on the same principles as Google Translate - instead of the Chrome Translate 🙂
In the Google-world, there are 2 translate mechanisms. If one were to paste the URL into the Google Translate UI, it would open a tab on the Google URL, with a frame displaying translated content. As you can see, this means that the website can no longer access its own cookies, and all state is lost. In fact can also brick some websites, due to CORS policies or required functional cookies.
Google has realized this a very, very long time ago, and within Chrome they built a "Chrome Translate", that utilizes GT's APIs to perform "inline translation" without changing the URL.
Unfortunately, Kagi Translate is the equivalent of Google Translate, not the Chrome Translate. This limits its use quite a bit. Especially in places where it truly matters.
I'd love to see a "real" Orion Translate functionality that performs inline translation. For me, and many others, this feature of Chrome is almost a deal breaker in any non-Chromium browsers. Safari has no viable plugins that do this, and neither does Firefox, as both of them have very limited translation capabilities (Apple Translate languages list is quite short). Kagi is in an unique position to do this, having already implemented Kagi Translate.
