Let Kagi extension redirect bangs

Thibaultmol

eirk I haven't actually looked it up but at least this proves that it's possible.

While this is good, these obviously wouldn't be synchronized to kagi's lists and def not include custom bangs you set.

But hey, kagi might be able to use the code if license compatible to add it to their app, and just add a syncing feature to it

Thibaultmol

sidenote: when making the docs for this feature: feel free to add that this helps with privacy because if the extension is installed, the query won't even be sent to the server? (i guess?)

LucasOe

Currently, you can use bangs either at the beginning or end of your query: !g query and query !g both work. However, if the query is a link, appending a bang doesn't work.

For example, !ccc [amazon link] works, but not [amazon link] !ccc. It's a minor thing, but having this feature would probably make it possible to have bangs work at the end of a link.

LucasOe

And keep in mind, that for the best results, this should also work with custom bangs. That means the Kagi extension would have to communicate with the servers to fetch the users' settings, in that case, a roundtrip to the servers is still required, unless the settings are stored or cached locally.

z64

It's highly unlikely we'll do this due to the added complexity & potential for bugs for little benefit. We're working on other solutions to more gracefully keep some level of service avaialable, even in the event we have to take the whole system down, things like this should still work.

Thibaultmol

z64 tbf, my use case wasn't necessarily with "what if kagi down" scenario's. but more so just:

privacy: any bang prompts won't go to kagi servers
speed: I think it'd be faster if the extension just has the bangs cached and can rediret you directly, so that half a second or second you have to wait on kagi to redirect you would disappear

z64

Yea those still aren't compelling enough for the implementation cost & risks. I am not even sure if we can practically implement it with limitations of browser extensions. The only way we would consider it is if it is opt-in and people are OK with having stale bang data (on the magnitude of ~months)

z64

... so that half a second or second you have to wait on kagi to redirect you would disappear

This sounds very wrong if that is the case. Measuring just with !g test, the Kagi redirect is on the order of 50ms. Even if you have to fully renegotiate SSL which involves a few more round trips, shouldn't be more than a few hundred ms.

Thibaultmol

z64 This sounds very wrong if that is the case. Measuring just with !g test, the Kagi redirect is on the order of 50ms. Even if you have to fully renegotiate SSL which involves a few more round trips, shouldn't be more than a few hundred ms.

Seems like Zen is just slow for this for some reason. Chrome/chromium does do it decently fast