But aren't you a part of the relevance equation? The ideal results for a search like [bitcoin crash] should be different for a Japanese-speaking searcher in Tokyo vs. a German-speaking searcher in Munich vs. a bitcoin expert vs. a programmer trying to diagnose why compiling bitcoin is crashing vs. my Mom who has never heard of bitcoin before, right?
Short version of long story: I used to bounce my net traffic through an ssh tunnel to a hosted VM. The VM was moved to a new machine in south-east asia. Having Google Toolbar constantly send my searches to the localized engine, despite the cookie selection, my being logged in and my preferences being clearly set, was more of a day-to-day annoyance than having my traffic piped across the Pacific twice.
For YEARS, on a weekly and sometimes daily basis, always logged-in, always with preferences set to english, it is infuriating to routinely end up receiving results that conflict with your explicit language settings.
What, concretely, do we have to do to get someone at google to push a change from using cookies to a real user-setting to fix this absurdity?
You said they did it for speed. Giving me completely incorrect results in a language I can't even read 1 millisecond faster than giving me results that I actually care about is a win? This is over-optimization.
I know I can use /ncr at the end, but I'd rather not have to do that all the time, and I think you can't even make that the default search for the Omnibox in Chrome, which means I have to give up Omnibox, which I love using, in order to get away from personalization. And even then, I think it just means I won't see my country specific results, but it probably still personalizes my search results through other types of signals.
So fine, don't make universal search the default way to search, but just give me a checkbox so I can turn it on when I want to. I want to see the best results, period - not the best results for me (or whatever Google thinks are the best results for me).