Kagi Bloopers – Search Results Gone Wrong
Postedabout 2 months agoActiveabout 2 months ago
help.kagi.comTechstoryHigh profile
calmmixed
Debate
40/100
Search EnginesKagiArtificial Intelligence
Key topics
Search Engines
Kagi
Artificial Intelligence
The Kagi search engine's 'Bloopers' page showcases amusing incorrect search results, sparking discussion about the engine's quirks, limitations, and value proposition.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
55m
Peak period
15
2-3h
Avg / period
8.6
Comment distribution43 data points
Loading chart...
Based on 43 loaded comments
Key moments
- 01Story posted
Nov 15, 2025 at 7:23 AM EST
about 2 months ago
Step 01 - 02First comment
Nov 15, 2025 at 8:17 AM EST
55m after posting
Step 02 - 03Peak activity
15 comments in 2-3h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 15, 2025 at 12:13 PM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45936964Type: storyLast synced: 11/20/2025, 8:56:45 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Yep that checks out
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.
I love it!
https://www.youtube.com/watch?v=8Ze6ZMkT2Z4 :-)
(though yes, they are funny)
https://help.kagi.com/kagi/settings/widgets.html
https://help.kagi.com/kagi/features/search-operators.html#qu...
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...
Really stupid bug that probably only happens with old.Reddit or RES or something. But it’s nice in that it keeps me off of Reddit I guess.
[0] https://www.aljazeera.com/news/2025/10/3/how-much-of-europes...
Recently it has not had such a strong quality margin, which I suspect is due to the AI slop that all of the search engines are fighting against (due to errors both ways in their detection). I'm hoping this is temporary.
To be clear, I don't use any of their features except search (and domain filtering).
If you need something that’s very noticeably better than its competition, then yes.
If you are okay with all of the terrible that comes with using LLM services as a search engine replacement, then probably no.
If you despise the amount of second guessing and source checking required to use LLMs as search tools, then yes.
Has access to kagi search which is a also a superset of search backends for the assistant
The initial false answer was baldly asserted by the LLM without sources in the first two paragraphs but some of the phrasing it used was enough to locate the non-authoritative blog content it was apparently laundering. Had it accurately cited sources, it would’ve been easy to see that this random WordPress site saying X wasn’t as authoritative as the PubMed hits saying !X.
I searched Kagi for “veterans day 2025” the other day (on Veterans Day, when I was unsure) and it answered
“= today”
19 more comments available on Hacker News