News for hackers. Stuff that matters.
Re:Why does searching Google for random hex almost always le... by SquareWheel on Friday May 31, 2024 @05:27PM (#40540455)
If you put quotes around the string (the "exact match" operator), the only results are this very thread. So it seems to be working as intended.

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.

Re:Why does searching Google for random hex almost always le... by underwater on Friday May 31, 2024 @06:13PM (#40540872)
But it’s clearly not what people want. Ask any person if a search for a hex encoded ID should be a fuzzy match for a different ID and the answer will be no.

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.

Re:Why does searching Google for random hex almost always le... by fragmede on Friday May 31, 2024 @06:41PM (#40541079)
Who is this "any person" who's searching for random hex, and how much do you think they care of Google shows them a car instead of whatever thing they're not even actually looking for?

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.

Re:Why does searching Google for random hex almost always le... by ipsum2 on Friday May 31, 2024 @07:32PM (#40541347)
Obviously no one would search a completely random hex, but it may represent an ID somewhere, and they want to find out more information about it. e.g. a SHA or MD5 hash.
Re:Why does searching Google for random hex almost always le... by fragmede on Friday May 31, 2024 @09:36PM (#40542123)
Agreed, you can look up d41d8cd98f00b204e9800998ecf8427e for example. The question is how critical is it that Google returns a non-useful result vs a page that says there are no results. I think most people don't care, it's not useful either way.
Re:Why does searching Google for random hex almost always le... by jkrejcha on Friday May 31, 2024 @10:26PM (#40542371)
As an aside, for those curious, it's the MD5 of the empty string :)
Re:Why does searching Google for random hex almost always le... by behringer on Friday May 31, 2024 @09:20PM (#40542024)
I search id's all the time. Google is becoming more and more worthless.
Re:Why does searching Google for random hex almost always le... by Dalewyn on Friday May 31, 2024 @09:15PM (#40541990)
>the world’s greatest search engine still doesn’t understand that you can’t fuzzy match an ID?

No, not without telling it to run an Exact Match search by enclosing the string in quotes.

Re:Why does searching Google for random hex almost always le... by semi on Saturday June 01, 2024 @10:31AM (#40546059)
> But it’s clearly not what people want. Ask any person if a search for a hex encoded ID should be a fuzzy match for a different ID and the answer will be no. >

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.

Re:Why does searching Google for random hex almost always le... by plorg on Friday May 31, 2024 @07:43PM (#40541404)
Meanwhile if I search for a specific Bosch solenoid part number there's a 50% chance that any one result will point to some different part number that contains 90% of the digits - even though the specific part number actually exists!
Re:Why does searching Google for random hex almost always le... by gravescale on Saturday June 01, 2024 @02:57AM (#40543512)
Same for electronic part numbers. Search engines will just go "eh, pretty close" and mix in results for, say, TPS562201 with those for TPS56221.
Re:Why does searching Google for random hex almost always le... by xp84 on Friday May 31, 2024 @06:48PM (#40541141)
I get that that's the default now, but can't help but hate it. When you search for like `dog house` to have a bunch of results for just house (marked "Missing: ~dog~" ) it's so dumb. Why would I have typed dog unless that was important to me??
Re:Why does searching Google for random hex almost always le... by OwenFM on Saturday June 01, 2024 @01:42AM (#40543192)
This sets things up for all sorts of problems when people don't notice that the IDs aren't exactly the same.

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"?