News for hackers. Stuff that matters.
Re:Why does searching Google for random hex almost always le... by CommieBobDole on Friday May 31, 2024 @01:26PM (#40537902)
Looking at this very briefly, the results seem to always be inventory pages for the dealerships, which use long strings of hex or just random numbers as identifiers for the vehicles they have for sale.

For example, a search for "ca7112b7167c15e621412c0fbc0a6c97" brings up the URL "https://www.premierclearancecenterofstbernard.com/inventory/...", which has a gallery of vehicles at the bottom whose image names are of the format "9b362510c100095f02cf3cad9e365ea6.jpg".

I assume something inside the Google black box is saying "well, there's no exact match but this site has a bunch of strings with most of the same characters, so here you go".

Edit: And to add to this, I'd surmise that the reason you see a lot of car dealerships in these results is that they sell a lot of one-offs - instead of having a list of SKUs in inventory, they sell a unique vehicle just once, so the inventory systems need to account for that by using long strings as item IDs and the like. Also there's probably a limited number of inventory systems out there, so a bunch of random dealerships are probably all using the same one.

Re:Why does searching Google for random hex almost always le... by cedws on Friday May 31, 2024 @03:04PM (#40539040)
Back when Google search was good this query would have returned no results. As it should do. Now it desperately tries to dig up anything it can find just so the number of results is not zero. Somebody at Google wanted to the increase search 'hit rate' KPI and this is the result.
Re:Why does searching Google for random hex almost always le... by noqc on Friday May 31, 2024 @04:06PM (#40539633)
Garbage in garbage out is fine here, no? I hate google quite as much as the next person here, but this seems like a non-issue. If I type in a random string, it should be assumed that I'm searching for something.
Re:Why does searching Google for random hex almost always le... by ryanianian on Friday May 31, 2024 @04:08PM (#40539663)
Sometimes you really do want exactly that "random" string. This is common with error messages, model numbers, build hashes, etc. If I'm searching for B9GDSIGH as the model number for my refrigerator, I really don't want to see B9GDSIGY.
Re:Why does searching Google for random hex almost always le... by kimixa on Friday May 31, 2024 @04:22PM (#40539795)
But if it links to the B9GDSIG series refrigerator, which has the 240v H and 120v Y subtypes, then it would be correct in suggesting that?

Same with error messages - they often have timestamps, or local object IDs/memory addresses, which you also want to be fuzzy-matched.

I think the issue is the de-emphasis of "power" modifiers for google - it's less obvious how to say "This part of the string needs exact match, this can be fuzzy"

Re:Why does searching Google for random hex almost always le... by dylan604 on Friday May 31, 2024 @04:51PM (#40540102)
In that case, click the "must contain" link and it resubmits with the query wrapped in quotes. Or, just quote the query yourself on the first go if you know it must match
Re:Why does searching Google for random hex almost always le... by ryanianian on Friday May 31, 2024 @05:00PM (#40540178)
Google no longer (hasn't in a while) respected quotes. It's very hard to get Google to actually say there aren't any results even when in fact there are no matching results.
Re:Why does searching Google for random hex almost always le... by dylan604 on Friday May 31, 2024 @05:36PM (#40540554)
They respect it when they submit it then, as every time I've used that function to see them update the query with quotes it comes back with different results. I've never cared to look at the search query in the URL, so maybe they also add and additional parameter that tells the back end specifically to obey the quotes on this resubmitting???? So at some point, the quotes aren't ignored
Re:Why does searching Google for random hex almost always le... by fragmede on Friday May 31, 2024 @06:43PM (#40541111)
that's not my experience.

https://www.google.com/search?q=%22kgirbudidndijrjjr%22 gives me "Your search - "kgirbudidndijrjjr" - did not match any documents.", at least it will until they index this comment and find kgirbudidndijrjjr

Re:Why does searching Google for random hex almost always le... by aldousd666 on Friday May 31, 2024 @05:06PM (#40540245)
on the advanced search, there's still the option to specify that it 'must contain' something, but I'm not sure if it's just a suggestion like quotes or not.
Re:Why does searching Google for random hex almost always le... by dylan604 on Friday May 31, 2024 @05:37PM (#40540568)
I "love" how we've reached a point where we so distrust this company specifically but dark pattern UIs in general where we almost anticipate placebo like buttons.
Re:Why does searching Google for random hex almost always le... by thfuran on Friday May 31, 2024 @05:01PM (#40540184)
Quotes are more like guidelines these days.
Re:Why does searching Google for random hex almost always le... by bravetraveler on Friday May 31, 2024 @04:13PM (#40539703)
One man's trash is another man's treasure. Search is ambiguous enough by nature IMO

Agree with the peer - specificity matters. Model numbers are a good example. I feel like I've developed a weak form of dyslexia because I can't trust Google.

Things I want fuzzy searches for... will be presented fuzzy. Not as an opaque string of characters, but wrapped in keywords

A reply makes a good point - double quotes don't seem as effective any more.

Re:Why does searching Google for random hex almost always le... by duxup on Friday May 31, 2024 @03:26PM (#40539273)
Is there anyway we can somehow find out that is true?

I could have sworn google always was happy to return some odd url matches, typically when the given results weren't great.

Re:Why does searching Google for random hex almost always le... by beardyw on Friday May 31, 2024 @04:09PM (#40539670)
There was at one time a kind of game where you tried to find a search term that would return only say 3 results. It was hard, but some did get found.

Having said that I have recently had some kind of "nothing found" result on several occasions. So it still happens.

--edit--

In fact I just tried "ca7112b7167c15e621412c0fbc0a6c9" (omitting the last digit to avoid HN) and got:

Your search - "ca7112b7167c15e621412c0fbc0a6c9" - did not match any documents.

Suggestions:

Make sure that all words are spelled correctly. Try different keywords. Try more general keywords.

Re:Why does searching Google for random hex almost always le... by doublerabbit on Friday May 31, 2024 @04:45PM (#40540042)
Google-Whack as I knew it.

Where you tried to find only a search with one result.

https://en.m.wikipedia.org/wiki/Googlewhack

Re:Why does searching Google for random hex almost always le... by cedws on Friday May 31, 2024 @03:37PM (#40539357)
Unless you have a time machine there's only anecdotal evidence, but there's plenty of it on HN. Seen many comments here reporting the same thing.
Re:Why does searching Google for random hex almost always le... by dylan604 on Friday May 31, 2024 @04:49PM (#40540087)
I've seen it come back with something along the lines of "it looks like there's not a lot matches" with some useless cartoon graphic.

I see this a lot when searching for phone numbers. I've also seen the opposite like the forced "find something no matter how terrible of a match to avoid no results" as being described. You search for a number and no exact matches, but it returns things with different area codes same prefix different numbers. Or same area code, different prefix, same numbers. Or some such randomness that I can't even venture a guess as to why it thought the not one number matches would be interesting to me. Unless you're brave, I'd suggest not searching for random phone numbers with Safe Search off as you'll find some very interesting pages displayed that have absolutely nothing to do with the number being searched.

Re:Why does searching Google for random hex almost always le... by rurp on Friday May 31, 2024 @05:04PM (#40540223)
I remember when Googlewhacks[0] used to be a thing. Zero result search queries weren't interesting enough because they were too easy to find.

[0]https://en.m.wikipedia.org/wiki/Googlewhack

Re:Why does searching Google for random hex almost always le... by Gormo on Saturday June 01, 2024 @03:33PM (#40548443)
Just do an image search for "google search returned no results screenshot". Plenty of examples.
Re:Why does searching Google for random hex almost always le... by refulgentis on Friday May 31, 2024 @03:06PM (#40539068)
That doesn't sound right to me: Google used to suppress results with string matches?

Why?

If so, would that be a good thing?

Why shouldn't I be able to find the vehicle via its ID?

Re:Why does searching Google for random hex almost always le... by risenshinetech on Friday May 31, 2024 @03:08PM (#40539093)
These aren't string matches. Check again.
Re:Why does searching Google for random hex almost always le... by refulgentis on Friday May 31, 2024 @04:47PM (#40540067)
Ah, doh, thank you.
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"?

Re:Why does searching Google for random hex almost always le... by shadowgovt on Friday May 31, 2024 @06:31PM (#40541005)
I can't tell you the number of times I've searched for random serial numbers and gotten the exact product I seek. I'm glad Google indexes this random crap.
Re:Why does searching Google for random hex almost always le... by Galatians4_16 on Friday May 31, 2024 @07:45PM (#40541417)
I miss when Google had thousands of results, and you could browse past page 5. Now it just lies to you.
Re:Why does searching Google for random hex almost always le... by 1vuio0pswjnm7 on Saturday June 01, 2024 @03:07AM (#40543557)
An experiment would be to create high quality, non-commercial websites with pages containing these hex strings and see if the pages appear in Google SERPs.

The fact that Google returns car dealerships when the user is searching for hex strings is telling.

Re:Why does searching Google for random hex almost always le... by libria on Friday May 31, 2024 @01:36PM (#40538024)
> no exact match but this site has a bunch of strings with most of the same characters

I suspect it's something similar, but more like partial string match which may score as "close enough to display". I get consistent results with the same hex string - dealerships - but if I quote it (exact match), I get no matches.

Re:Why does searching Google for random hex almost always le... by rerdavies on Friday May 31, 2024 @02:48PM (#40538886)
I suspect there's a single word embedding for WTF_IS_THAT.
Re:Why does searching Google for random hex almost always le... by confused_boner on Friday May 31, 2024 @06:15PM (#40540892)
Bing search results for that are interesting
Re:Why does searching Google for random hex almost always le... by shadowgovt on Friday May 31, 2024 @06:30PM (#40541003)
Additionally, the user is doing the search in a non-Incognito session, so the system will bias based on assumption of user preferences. "Hm, I see this random hex identifier in three pages... Oh, but this user likes cars. Let's give 'em the car result first."
Re:Why does searching Google for random hex almost always le... by wlesieutre on Friday May 31, 2024 @07:37PM (#40541370)
> Edit: And to add to this, I'd surmise that the reason you see a lot of car dealerships in these results is that they sell a lot of one-offs - instead of having a list of SKUs in inventory, they sell a unique vehicle just once, so the inventory systems need to account for that by using long strings as item IDs and the like.

If only there were some sort of standardized identification number for vehicles

Re:Why does searching Google for random hex almost always le... by alanh on Friday May 31, 2024 @07:56PM (#40541503)
I DO NOT BUY IT. Plenty of sites use unique identifiers and other random hex strings all over, e.g., fingerprinted assets. If your explanation were accurate I would expect more kinds of sites to show up