3 ms·
My guess is that if you do user research you'll find that for the vast majority of people exact token matches are not what they actually need or appreciate. Pe
by simonw 4y ago
My guess is that if you do user research you'll find that for the vast majority of people exact token matches are not what they actually need or appreciate.
People run searches on their phones with typos. They don't have a good mental model for how search works, or how best to use it. If they search for "can puppy eat pork" they're actually looking for results about if dogs can eat ham.
As an expert user of search this infuriates me too, especially when tricks like double quoting don't get me what I'm looking for.
But as someone who often implements search engines I'm spending a lot more time thinking about fuzzy matches and semantic search (things like searches that use vector embeddings generated by language models).
- andrewstuart 4y agoIronic.
- xg15 4y agoWeren't "advanced search" UIs and the old convention of using quotes exactly for this? Use fuzzy search as default, switch to exact search for everything written in quotes. Where would be the problem? The convention is well-known enough that even nontechnical users wouldn't be surprised by it.
- cosmotic 4y agoI prefer exact matches with fuzzy appended to the end.
- jfoster 4y agoThere's value in fuzzy matches, but defaulting to complete fuzzyness always is not a good way of attempting to unlock that value.
- dcminter 4y agoI confess that sometimes the fuzzy matching is useful. I do not always know what the keywords ought to be. But sometimes I do - and I die a little when there's no way to express that. By the by I remember that one of the things that made me switch to Google from AltaVista was that Google were indexing the term "C++" as being distinct from "C" which obviously made a big difference to the utility of the results!