SpacemanSpiff

Weird, they do, but they redirect for me and the final URL is different than what you pasted.

https://help.kagi.com/kagi/getting-started/

https://help.kagi.com/kagi/why-kagi/why-pay-for-search.html

My best guess is that a DNS record is messed up on their end, and since I’ve been to those pages before relatively recently, the cname or A-record is still cached for me.

Hmm I just checked, they’re all live and their status page for each link has no outages. I would check any content blockers etc. that you have, I suspect it’s a problem on your end. They do use different domains for their blog, feedback, and help KB etc.

Kagi does exactly what you’re describing. It’s what I’ve been using.

Yes….on a technical level. But the picture is bigger than that. Personally, I have a hunch that the choice of Rust is making Lemmy’s development slower. This seemed to be evidenced by the fact that Kbin has more functionality than Lemmy while having only been around for 2 months. Vs Lemmy’s 4 years. The Kbin dev has also been much more able to fix things on the fly during the surge in users. Whereas Lemmy will supposedly move off websocket use any day now.

Adoptability isn’t something to be discounted. The fact that there any more people out there familiar with PHP may give Kbin an edge over time. And let’s be honest, in real-world test PHP can very often be faster then - less-than-mature-Rust codebase.

They do have their own crawler and I believe supplement from bing only when necessary. Something like 96% of results are from their own index. They actually have a breakdown for every search.

Currently using Orion on iOS. It’s made by the same people behind the Kagi search engine (which I also use now).

It’s still in alpha, so I occasionally encounter a bug, but the fact that it has built-in advert and tracking protection, as well as cool tab-suspend features sold me.

It tends to be on a newer version of WebKit then then Safari as well.

Oh, and did I mention it can use both Chrome and Firefox extensions?

I think Google peaked about 6-8 years ago now and then started slipping at an ever accelerating rate.

It’s almost useless for me when searching anything remotely technical or otherwise niche.

I almost consistently need to go to the second page of results now, something I don’t remember doing since like 2009.

I find Bing acceptable. Brave search works well. But I’m actually using Kagi now since I’m hoping their paid model will actually mean I’m not the product.

Via the ActivityPub protocol that fediverse software uses :)

Pretty cool stuff!

Kbin can also directly interact with Mastodon users and toots because of this. Kbin magazines can natively contain both “threads” from Kbin and Lemmy, and microblog “posts” from Kbin and Mastodon. (And other software depending how they map these features.)

You bet! The fediverse is definitely a confusing concept to wrap your head around the first time. And it doesn’t help that different software server instances don’t need to use a site name that specifies which software they are (like Beehaw, for example).

I think the “dynamic updates” behaviour is tied to Lemmy’s use of websockets instead of http. Kbin uses http. The Lemmy devs have stated they’re going to move off of websockets in the future as they present scaling issues with the way the software is written.

The websocket protocol allows bi-directional push communication regardless of the previous request which means that new posts are constantly triggering server side updates which then appear like a page “refresh” on clients.

Arguably, while websockets have very cool realtime features compared to http, for a Reddit-like content aggregate their use can quickly overwhelm usability without significant retooling.

It depends on what you mean by other servers…Lemmy instances? I haven’t seen any differences between kbin instances.

Kbin is entirely different software from Lemmy; it’s a completely different backend.

So that would be why it’s “better” in that regard than Lemmy instances. My understanding is that it’s a bug in Lemmy that will be fixed soon.

The “popping” of the feed in Lemmy is tied to their use of websockets instead of http. I believe the devs stated they’ll be moving off of websockets in the future.

Also using Orion! It’s the only one that’s convinced me it’s better than Safari, primarily because it’s actually more aggressive with power savings than Safari. The implementation to kill idle tab processes almost immediately is very effective imo.