Isn't this just catching up? Google has site:reddit.com, it's more keystrokes but a lot less idiosyncratic and thus generalizable to any domain.

Kagi is becoming the new google. Same thing, offered in a new package. If there are 100 good results for a query, why always show the same results in the same order?

Will this allow kagi to be used on the forced search widget at the bottom of the screen of pixel phones ?

Because the blog mention that Google will be forced to propose kagi in the default search engine list given 5k installs, but even with it installed I cannot set kagi as my search engine on that widget.

On the contrary if I install duckduckgo or bing, I can choose one of them to replace Google in that widget.

EDIT: android itself talks about the 5k limit for the "choice screen" during initial setup [0], but there is no mention of how the list is populated afterwards

[0]: https://www.android.com/choicescreen/dma/searchengine/

Why would an app be a requirement for a search engine? To me it would make more sense to be aligned with how many users the search engine has. 5,000 unique per month, or whatever.

I have the Kagi app on my iPhone, but just so it can be an extension in Safari. In a perfect world, I would be able to go into the settings, add a custom search engine, and be done with it. No app or extension needed. Then when it hits a threshold it can be added as an easy option for people to pick from a list.

We do currently have a field to override the domain used for snaps (the `ad` field in the bangs repository[1]) which doesn't have much validation and is useful for situations like this. It's possible we'll expose this for custom bangs in the future, but for now I can add that as a bang to the main repository, as it seems like it would be generally useful.

[1]: https://github.com/kagisearch/bangs?tab=readme-ov-file#bang-...

I would normally agree. But Kagi's AI thing doesn't annoy me in ways it does in other products. End a query in a "?" to get a quick summary with links to the sources. Normal search results below.

Check the latest release notes for all search improvements that went out in this release:

https://kagi.com/changelog#4813

I have stopped to pay Kagi because their obsession to employ AI everywhere.

You can create a custom lens that includes those sites and point a custom bang at it.

For example I have a custom QT lens that only includes results from [*.qt.io, *.stackoverflow.com, *.github.com...] and a !qt bang pointing to it at https://kagi.com/search?q=%s&l=8

(you'll have to change the l= id to point at your lens)

I would also say that probably this feature was nearly custom made for Reddit and there are few other sites that you would probably use it on. For this feature to be useful, a few things need to be true:

1. The site has a lot of content worth parsing such that it's worthwhile to limit your search to only that site.

2. The site itself has a garbage search functionality that you would not want to use instead

3. You need to be searching that site frequently enough that there is a need to shorthand it instead of typing out the long form syntax

4. The site must have content that is generally picked up best by a traditional search indexer e.g. mostly be text based in what you want to search

There are relatively few sites like that in existence. Probably if I mentioned the above requirements to anyone well versed in internet, Reddit would be the immediate first example out of anyone's mouth. Perhaps there are a few other sites that might meet the mark (Stackoverflow and Github come to mind in my example, or possibly other social media giants heavier in text based content as well. Or Hacker News, ofc). But most other large sites' search story is better enough that even then I would probably not naturally use this feature instead.

> What would be super awesome, imo, would be if I could assign "some sites" as a short code, then snaps that.

My app https://multi-launch.leftium.com already does that! (Except with buttons; bang triggers coming soon...) Note you need to give browser permissions to open pop-ups, otherwise multiple tabs cannot be opened.

- Docs/examples: https://mm.leftium.com/doc

- All buttons share the (text) input at the top. ENTER inside the input triggers the first blue button.

- Blue buttons launch all dark gray links in their category.

- Gray buttons launch individual links.

- Light gray buttons are excluded from the launch group (but they can be manually launched.)

Recently I realized bangs and launch buttons are just bookmarks. So I'm currently combining these concepts so you can launch bookmarks or groups of bookmarks with a bang trigger. (As well as take notes for a URL!)

---

- The very first iteration of this idea launched multiple images searches at the same time: https://is.leftium.com/

- Now implemented as a launch group: https://mm.leftium.com/?p=C4S2BsFMAIF5oEQEkC2BDA5jAypNAnAYwA...

You can already do that with Kagi lenses (if I understand you correctly)

Such as Albert? [0]

[0]: https://albertlauncher.github.io

It appears to be a UI thing, but it's an excellent UI thing: it reuses familiar bangs and has an autocomplete/discovery mode for new bang codes.

Marginally quicker to type:

@r vs site:reddit.com

After a few tries, I also find the first more intuitive.

I'm sure it's highly likely google will either heavily deprecate/drop this feature altogether. It's already happened with other query tricks.

Less typing

Is it worth investing early in better things so they have a chance?

Yes.

The worst that can happen is the better thing goes away again, and your payment goes away too.

Kagi is already profitable and organically growing, so at least from a financial standpoint the future is certain.

If Kagi goes away, it should be relatively easy to switch to an alternative :-)

Kagi has bangs. This is different. It's a shortcut for "site: somesite.com", while a bang just redirects to the somesite.com search results page.

Sick idea. We’ll need an OpenSearch or equivalent cluster indexing your local fs right? Can we do this just in browser (and would we even want to)?

It clearly shows in the example that @r translated to "site:www.reddit.com" in their resulting search- I did not read "supporting domain search in general" as being Kagi specific.

The Kagi specific part is /easily/ searching a site in Kagi.

The whole point here is that they are extending the already supported bangs[1] to search the domain with "@", thus if "!r" exists to redirect to Reddit's search, you can use @r to search Reddit within Kagi.

Of course I could type "site:Reddit.com" that's what I've been doing for years, including on Kagi, but easily doing that with @<bang> seems exclusive to Kagi.

[1] Kagi maintains an open source list of supported bangs here, you can even do a PR to add even more: https://github.com/kagisearch/bangs

All you have to do is not cut off (in the quote) the obvious ergonomic difference between a short code

@ lsm

and a long one

site:long-site-naem-with-a-ttpo