Kagi should be more tolerant to user input style & errors (focus on meaning more than syntax)

MustafaD

This feature improves search query processing to make it more tolerant to user mistakes, typos, hastiness, etc, as users have come to expect from search. A similar issue is #10211.

Coming from Google and expecting a Google-like experience, but better. This is something simple that nags.

Screenshot demonstrating case sensitivity of Kagi to search keywords ('Define cool'≠'define cool')

Google has taught us that if I say 'define: word' or 'define word' or 'defien word' or 'DEFINE word' or 'Define word' etc, it all means "define this word".

By being fuzzy I mean, Kagi should be tolerant to misspellings, different letter casings, etc. Kagi already does a good job of equating 'cool define' = 'define cool' = 'cool definition'.

I just hope it allows for misspellings and things like 'Define cool'.

This applies also to other search modifiers/shortcuts/keywords like 'calc 50+30' = 'CALC 50+30' = 'Calc 50+30' = 'callc 50+30' = 'cacl 50+30' (only the first one fires the calculator widget as of now).

JosephT

u seem to be putting the service through the testing gauntlet, how are u finding it? i couldn't understand the issue because your example already looks to satisfy it, but thats your search customization.

MustafaD

JosephT I want it to be tolerant with: spelling mistakes (eg: 'defune atone'), messy order (eg: 'atone define'), and case (eg: DEFINE ATONE).

Here is an real example of why the current situation is inconvenient (compared to Google Search):
Example of incorrect results for 'defune atone' and 'DEFINE ATONE'

This really should be fixed 😔.