This is not revolutionary but it saves some keystrokes when wanting to limit results to certain sites.
Personally I don’t really limit anything with Kagi. It’s usually just finding what I want without having to do anything.
This is not revolutionary but it saves some keystrokes when wanting to limit results to certain sites.
Personally I don’t really limit anything with Kagi. It’s usually just finding what I want without having to do anything.
I kind of wish that they’d unify some of their features.
For example, I use the “Fediverse Forums” search lens to search the Threadiverse only. That’s a drop-down menu.
Then there are those Duck Duck Go-style alias things that start with an exclamation mark.
kagis
Bangs.
And now the snaps.
Like, is it necessary to have all these as separate, segregated features? They all kind of do the same thing, are a way to ask the search engine to interpret the query differently.
EDIT: Also, I don’t know if there’s a Kagi lemmy community, but if so, that might be a better place than [email protected], since most folks won’t be using Kagi. Doesn’t matter much for communities that are desperate for traffic – like, for games, I’d rather talk on a general games forum until traffic hits some point, rather than having a lot of game-specific communities that are ghost towns. But [email protected] is one of the largest Lemmy communities, probably has enough post throughput.
I’m not a mod, not saying that it’s community policy, just thinking about where it might best make sense.
EDIT2: Looking at lemmyverse.net, there is, but it’s on lemmy.ml, and I’d really rather not subscribe to .ml communities. Doesn’t appear to be any other Kagi communities at the moment.
Well, I don’t really want to mod one myself, but if anyone wants to run a Kagi community somewhere off .ml, I’ll subscribe.
Agree, there’s a lot going on. How I see it:
@xxx are snaps, limiting result to any resource from a website e.g. Wikipedia.com
!xxx are bangs, using the sites own search engine to return results. They are external searches, and might provide more (if the site does not expose certain parts to search engine) or less (if the site didn’t build search capabilities for some parts but they are indexable) than snaps.
Lenses return search results based on certain criteria. Those could be a list of snaps (so domains), but also geography, keywords, file types, or they could exclude the same.
You have a point about posting in this community. But if you think about it, Lemmy doesn’t have enough traffic to make it useful to have millions of communities.
It would be enough to have 50 communities and each one would have decent traffic. The only reason there is more is because people copied reddit and figured they would have users coming to their community. But most are really struggling, because the cheese is spread too thin.
What is threadaverse? Like Threads implementation?
Nah, the Reddit-alike thread-based intercompatable forum systems on the Fediverse. Lemmy. Kbin. Mbin. Piefed. Sublinks.
A bit of a hot take. The only real difference between Lemmy and Mastodon is sorting of the posts, everything else is UI. You can have Mastodon experience very similar to Lemmy although it breaks a bit with high traffic. It’s actually quite useful to subscribe to low traffic text based Lemmy communities via Mastodon because new comments bump old threads and it’s kinda like old forums, especially in a client with threaded view.
Tap for spoiler
Phew!!
That sounds much better