Hacker News new | comments | show | ask | jobs | submit login

> Seems they ae trying to tell me that although I searched for something they know that I really wanted something else.

Consider: maybe you know the keyword that should be in the document you want to find... but the author of the document you want to find, didn't use that keyword. Instead, they used a synonym for it, because they were unaware of the idiomatic keyword to use.

Example: medical journals. Eventually, everyone agrees on what the term for something is. But the very first few papers on that thing, might not call it that, because they were inventing it.

Do you want to fail to find those first (and most important) few papers on the subject? Or do you want Google to do the text-parsing equivalent of "snap to grid", ensuring that documents that say the right thing the "wrong" way still show up?

As far as I can tell, as far as the output goes, correcting your language and correcting the document's language are basically indistinguishable. Google could just be thinking of what it's doing as the latter, and yet it ends up having the same effect as the former.

This is fine and nice by default, but there should be a way to disable it. Sometimes you are really searching for a specific word, and really don't want any other substitution.

I see it a lot Google searching for electronics terms, where combining common and unusual term sometimes causes unusual term to be ignored. The quotes used to help, but they no longer do.

Except that is exactly how PageRank worked in the beginning. Heavily linked pages were deemed more popular/useful while those at the edges of the network were less so.

As for your last point, metadata is all about addressing these issues. The context has to remain canonical, otherwise God knows what sort of legal issues would arise.

It seems to me there is a trend towards always correcting user input. This may often work but somehow I am looking for something very specific and I don't want a synonym.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact