I guess for "Pop os" it gave a 2004 estimate for the population of the Cocos Islands. https://www.axl.cefan.ulaval.ca/pacifique/cocos-ile.htm
More likely the town of Os in Innlandet, Norway, which was around that population a year or two ago.
Kagi Bloopers – Search Results Gone Wrong
11–20 of 66 posts
Re: Kagi Bloopers – Search Results Gone Wrong
#12“Pure numbers and French are not compatible” Yep that checks out
Sixty-ten-eight! Sixty-ten-nine! Four-twenties! 1999 == One thousand, nine hundreds, four twenties, ten, nine. I studied French in grade school over ten years and I love it. But the way numbers convert into language is wild. I tease it with love.
Switzerland and Belgium got them right!
Re: Kagi Bloopers – Search Results Gone Wrong
#13Given the title "Search Results Gone Wrong", I'd like to take this opportunity to try to shame Kagi into fixing the search results for the "More results" feature. This simple feature is broken in that it often gives you repeats of the same initial results it gave. That is, instead of giving you "More results", it gives you a lot of "Same results".
I reported this as a bug about 6 months ago, and was quickly told it was planned to be fixed. But it hasn't been fixed. I checked in again a few weeks ago to see if there was any progress, and apparently they've given up because it is too hard: "Apologies, seems I forgot to update the thread. Unfortunately it is in fact trickier than it looks to dedupe these results. Mainly this is a result of how we work with results from upstream sources, and deduping is heavily complicated by caching issues."
Kagi, you're generally great. I'm usually happy to be a paying customer. But I refuse to believe that deduping a list of URL's is actually too hard for you. Maybe I'm one of the few users who actually cares about searching for web pages, but for my use cases my search results would be much better if you actually gave me more results when I click on "More results". How is this not considered core functionality for a search engine? Please fix this!
Here's the bug report: https://kagifeedback.org/d/7022-clicking-more-results-yields...
Re: Kagi Bloopers – Search Results Gone Wrong
#14[dead]
Re: Kagi Bloopers – Search Results Gone Wrong
#15I guess for "Pop os" it gave a 2004 estimate for the population of the Cocos Islands. https://www.axl.cefan.ulaval.ca/pacifique/cocos-ile.htm
[dead]
Re: Kagi Bloopers – Search Results Gone Wrong
#16Just going to drop a quick complaint here that none of these are search results . (though yes, they are funny)
People searched for something; these were the results. What else would you call it?
If we use the strict definition of organic results in SERP, these aren't the result of webpage indexation, they're the output of widgets and other natural language parsing in Kagi.
https://help.kagi.com/kagi/settings/widgets.html
https://help.kagi.com/kagi/features/search-operators.html#qu...
Re: Kagi Bloopers – Search Results Gone Wrong
#17Is Kagi worth paying for? It's been on my radar for a while.
Re: Kagi Bloopers – Search Results Gone Wrong
#18“Pure numbers and French are not compatible” Yep that checks out
Sixty-ten-eight! Sixty-ten-nine! Four-twenties! 1999 == One thousand, nine hundreds, four twenties, ten, nine. I studied French in grade school over ten years and I love it. But the way numbers convert into language is wild. I tease it with love.
> Sixty-ten-eight! Sixty-ten-nine! Four-twenties!
Re: Kagi Bloopers – Search Results Gone Wrong
#19Does Kagi have any value in the era of LLMs? My understanding is that it aggregates result from different providers.
Re: Kagi Bloopers – Search Results Gone Wrong
#20Just going to drop a quick complaint here that none of these are search results . (though yes, they are funny)
People searched for something; these were the results. What else would you call it?
Those used to be called "instant answers" before every search engine renamed them to "AI overviews".