Gregory's Server@rodhilton Not that this contradicts the main point (that Google Search is over, which I agree with) but this same query in Google for me provides the correct result. Incredibly low bar but it does come back correct.
|
19 comments
@rodhilton that was what I was assuming as well - so egregious and with enough visibility that a manual fix was required. 100% agree with your thesis - if you’re looking for a fact which is known, Google no longer useful as a way to get it @markusl @kaup @Caryjm @rodhilton I just tried it too, still not patched 7:49 pm Eastern. I also provided feedback asking them not to provide chatgpt responses as top hits.  @therionofthebeast @rodhilton @Caryjm Crap. #Startpage doesn't filter that crap out (probably no way to), so it shows the same bullshit results. Time to switch search engines. @rodhilton @Caryjm It still produces the incorrect result as of this post. The suggested search query omits “the letter” from the query (see my other comment) which produces a correct result.  @ClickyMcTicker @rodhilton @Caryjm: Unfortunately, I appear, even without "the letter", to get the incorrect result.  @rodhilton @Caryjm still the same now from Germany on google.de @rodhilton @Caryjm FYI, I just tried it 18 hours after your comment and still got the “Kenya doesn’t start with K” response from Google. @Caryjm @rodhilton I couldn't believe that this was anything but an urban legend so I queried Google. Sure enough, it give me the bogus chatGPT answer. #DuckDuckGo gave me a reasonable and accurate list of websites with the right answer. Google, you are dead to me. @Caryjm @rodhilton Did you type “country in Africa that starts with the letter k” or “country in Africa that starts with k”? The former produces the result seen above, and the latter produces the result you received (albeit that same result is the second on the list behind the correct answer) |
@Caryjm the fact that Google was doing this went viral on a lot of socials and I believe there was a frontpage HN post about it as well, so Google has patched the query to fix this. It's working for me now as well.