Lens won't limit search to configured sites

dazzo

I have a lens that's just for Reddit. It used to work and would only return reddit.com results when the lens was turned on, but I noticed in the last day or so that it no longer limits results to the reddit.com domain. I have not changed any settings to get to this state. I've attached a screenshot of my lens configuration and a screenshot of search results when that lens is turned on.

I expected that the only returned search results would be from the reddit.com domain given the lens configuration.

rz

same for me

technobabble

Same issue, same site, same lens configuration.

akiselev

This is happening to me too with a custom Reddit bang that overlaps with the official reddit bang. Other custom bangs that don’t overlap with built in ones work.

I’ve seen this bug before last year

Kageon

Same for me. I created a new lens called "Test" with the site "reddit.com" and it worked again for a short time. Then I disabled the old Reddit lens and renamed the new one and added a description and it continued working. Then I moved it to the top position in the lenses view and it stopped working again. Then I deleted the old Reddit lens completely and now it is working again (except a few searches that got cached when it wasn't working).

Very weird behavior, I did have the custom bang set to 'r' which overlaps with the normal Reddit search as akiselev suggested, but I've had that for months and the issue just started occurring today for me, so I don't think that is the problem. Also the new lens never had the custom bang and it also wasn't working for a short time.

Edit: It stopped working again

spitfire

Same thing happening to me, same Lens too.

Krmloo

Same problem, both my custom Reddit lenses; started yesterday

jvbf

Can confirm this is a real problem. I also have a lens for Reddit, and sometimes it just doesn't work at all.

Chris

Description

I had a weird situation where a very specifc search query shows results that don't appear to be using the Lense at all. The results are worse than no lense.

The lense I'm using: https://kagi.com/lenses/mv7d8Ur89wDU1lb2P77thoHHKCaYmhg6

Steps

All I did was:

Search "!pc check if mouse locked" from the Firefox URL bar.
This shows results with my "PlayCanvas" lense. (Note that PlayCanvas has a default bang with !pc, my lense overrides that default).
The results I get are completely irrelevant. They don't use any of the sites in my lense. They're even less relevant than the default no-lense search results.

Expectation

I've used this lense a lot and I've never seen results this far off what I was expecting. I expected at least some of the domains I entered into this lense, I see no relevant domains.

The bug seems relevant to the very specific search query I used. If I just add "test" at the end of my query, suddenly the results are what I expect. In fact, as long as I don't use the same exact query, the results look fine. Which makes me think this is caching related.

Even worse than non-lense results

Even if I turn off the lense all-together, the results still look better than the results I got for "!pc check if mouse locked". I realize I have MDN pinned in the screenshot below, but overall it shows more coding-related results, while my bad lense search was showing a ton of IT/customer support results.

Chris

Update - actually this seems to be happening EVERY TIME I search with !pc <search query here> from the search bar.

Searching on kagi.com works

Now when I search "check if mouse locked" from on the kagi.com website, the results now look correct.

Searching with the !pc bang in the browser URL does not

But, because I recently tried "!pc check if mouse locked test" from the browser URL bar. "check if mouse locked test" now shows incorrect resuts, even when searching from the kagi.com website.

Caching

Caching means after searching with !pc in the browser URL, any subsequent search (for a time) will be incorrect when searched from the kagi.com website as well.

!pc bang

Whether the search is done from the browser URL bar seems irrelevant. This bug always happens when I use !pc, regardless of whether the search is on kagi.com or my browser URL bar.

Thibaultmol

I tried some things, but I can't reproduce this. What browser are you using? I doubt it matters, but yeah

z64

Hey all, thanks for the examples & your patience. We identified the issue and are rolling out a fix now! Should be available globally in approx. 1hr.

z64

This should be resolved now.

technobabble

z64 Thanks for the quick fix!