As technical people, it’s easy to infer what’s happening under the hood and make excuses for the weirdness. But food product design is about having strong opinions about what should happen, and ignoring our bias is around the limitations of the tech or the status quo.
In an age where I can have an entire conversation with a computer or generate a video from text the world’s greatest search engine still doesn’t understand that you can’t fuzzy match an ID? It increasingly feels like Google search is stuck in the past.
the idea that this mythical "any person" even cares about the difference between a useless car result and a page that says no results and then they just move on with their lives is projecting a lot of your own biases onto a hypothetical.
No, not without telling it to run an Exact Match search by enclosing the string in quotes.
in a search field explicitly for hex encoded IDs it shouldn't be
In a generic web search that has to guess if my term was a hex encoded id ('cafe' is but almost certainly isn't intended as one..).. it's less obvious.
in the case of a clear hex encoded id of sufficient length, i would like to know there are zero exact results, but as long as it's still fast I would love some fuzzy matches after in case there was a typo in my term or in the indexed document.
At the moment, Google happens to be choosing car dealers as a fallback, but what if it instead fell back to a page "transaction a67cedf has been confirmed"?
Basically, you did a fuzzy search and got a fuzzy result. Usually that's what people want. Quotes will let you fine-tune results. Or if you want all results to be strict by default, use verbatim mode. I tested that with the above string and again, only this thread showed up.