131–140 of 168 posts
Earlier quoted context omitted.
If only Google had some sort of "account" system that could store user-specific preferences...
It'd be better if we could just append a "v" after the URL to make verbatim searches. That way we can bookmark it and there will be no need to be logged in.
&tbs=li:1
Earlier quoted context omitted.
It'd be better if we could just append a "v" after the URL to make verbatim searches. That way we can bookmark it and there will be no need to be logged in.
You can. Append: &tbs=li:1 Ugly, but it works.
You may have to add your own to the list:
hXXp://www.google.com/search?q=%s&le=en&start=0&tbs=li:1
I know that a lot of people were sad that we switched from +word to "word" to do an exact match for a word. The good news is that we're rolling out a "literal mode" that will search for exactly the words you typed. It does a verbatim match with your words, so it turns off things like spelling corrections, stemming, synonyms, optionalized terms, and so on. I think we saw multiple proposals for this on Hacker News, so…
halo -"halo 2" -"halo 3"
And, of course, the "search for what I actually fucking typed" mode is completely undiscoverable, hidden behind another click, and which can't be defaulted into. This is a good bandaid, but is still a bandaid. I have still switched away from Google to a search engine that will actually search for what I told it to, not one that thinks it can guess my meaning. (Not to mention one that doesn't wrap all the outgoing URL…
For the vast majority of users, things like spelling correction are a huge help. Roughly 10% of all queries are misspelled. Switching the default to "search for exactly what I typed" would hurt those users and lead to more spam and malware for the average user. We try to find the balance that helps users the most, and searching for a term with "term" or the literal mode provides an escape hatch for power users.
If you want to default considering some words optional, that's fine. But say that above the search results.
I think it's forgotten in this discussion that the HN community is probably very different from the larger internet population when it comes to search queries. We all tend to do a lot more "exact/verbatim type searches" such as looking up some library package, whereas your regular user has a lot more "soft" queries where they're looking for a concept / business / song lyric rather than an exact phrase, and having pro…
Counter example: I just tried googling [how pronounce resig]. It thinks I want [how pronounce resignation]. Both +resig and "resig" didn't work (heck, I even tried +"resig"). Had to add -resign -resignation. There is nothing technical about this search (unless Resig is such a unique last name that belongs to only John Resig). I'm sure there's lots more counter examples. I really doubt normal non-technical people actu…
I think it's forgotten in this discussion that the HN community is probably very different from the larger internet population when it comes to search queries. We all tend to do a lot more "exact/verbatim type searches" such as looking up some library package, whereas your regular user has a lot more "soft" queries where they're looking for a concept / business / song lyric rather than an exact phrase, and having pro…
Counter example: I just tried googling [how pronounce resig]. It thinks I want [how pronounce resignation]. Both +resig and "resig" didn't work (heck, I even tried +"resig"). Had to add -resign -resignation. There is nothing technical about this search (unless Resig is such a unique last name that belongs to only John Resig). I'm sure there's lots more counter examples. I really doubt normal non-technical people actu…
Earlier quoted context omitted.
For the vast majority of users, things like spelling correction are a huge help. Roughly 10% of all queries are misspelled. Switching the default to "search for exactly what I typed" would hurt those users and lead to more spam and malware for the average user. We try to find the balance that helps users the most, and searching for a term with "term" or the literal mode provides an escape hatch for power users.
Personally, I like the previous "did you mean" behavior; if Google thinks I misspelled a word, or that I want a synonym, by all means give me the alternative, but by default I want the exact query I searched for, because more often than not I really did mean what I searched for rather than what Google thought I meant.
I know that a lot of people were sad that we switched from +word to "word" to do an exact match for a word. The good news is that we're rolling out a "literal mode" that will search for exactly the words you typed. It does a verbatim match with your words, so it turns off things like spelling corrections, stemming, synonyms, optionalized terms, and so on. I think we saw multiple proposals for this on Hacker News, so…
Still waiting on being able to search for punctuation. Being able to search for "$. ruby" or "$_ perl" or "$: edit: Just realized "$_ perl" actually does work. It would be nice, however, if we could search for these kinds of terms generally and not just in specific case.
Earlier quoted context omitted.
Counter example: I just tried googling [how pronounce resig]. It thinks I want [how pronounce resignation]. Both +resig and "resig" didn't work (heck, I even tried +"resig"). Had to add -resign -resignation. There is nothing technical about this search (unless Resig is such a unique last name that belongs to only John Resig). I'm sure there's lots more counter examples. I really doubt normal non-technical people actu…
[how to pronounce "resig"] works for me now. (Or at least doesn't mess with the query, though the results aren't great.) Do you remember what results you were seeing before?