3 ms·

"Snaps is an exclusive Kagi Search feature that allows you to easily limit search results to a specific website..." WTF is this marketing bullshit?! Default Go

"Snaps is an exclusive Kagi Search feature that allows you to easily limit search results to a specific website..." WTF is this marketing bullshit?! Default Google Search is useless now and I'm rooting for Kagi, but this "exclusive" untruth is decidedly NOT the way to "win". Google's "site:<domain>" search has been around for years: https://developers.google.com/search/docs/monitor-debug/search-operators/all-search-site https://developers.google.com/search/docs/monitor-debug/sear... Not related, DuckDuckGo's "bangs" https://duckduckgo.com/bangs https://duckduckgo.com/bangs which has, likewise, been around for years. *sigh*

deleted 2y ago
[deleted]
ajdude 2y ago
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 https://github.com/kagisearch/bangs
- calmbonsai 2y ago
  My concern was not with the ability to do the "site-specific search", but the bullshit regarding this feature to be "exclusive" to Kagi. If you're saying a different syntax makes something exclusive, I have some highly non-performant macros to sell you.
eviks 2y ago
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

deleted 2y ago

[deleted]

ajdude 2y ago

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 https://github.com/kagisearch/bangs

calmbonsai 2y ago
My concern was not with the ability to do the "site-specific search", but the bullshit regarding this feature to be "exclusive" to Kagi. If you're saying a different syntax makes something exclusive, I have some highly non-performant macros to sell you.

eviks 2y ago

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