I use Kagi too, it’s surprisingly snappy! Like seriously impressive for a small org. They talk about speed optimisation being critical for them as well. I find the result to be excellent as well. A true Google replacement/feels like Google in its prime.

I believe they have their own index and bot as well?

This is good news! And we/they should keep pushing for more, everywhere. Good for IBEW for continuing the pressure.

It would be pronounced “kaybin”. Like the Linux directory /sbin. It’s basically a name technical people would appreciate in a pun sort of way.

Nothing wrong with community, the point is Lemmy create the term the same as Kbin created magazine. Not every microblogging site in the fediverse calls them “toots” for example.

Really? Kbin as the name is what intrigued me initially over Lemmy. It’s actually inspired by Linux, the sbin directory to be specific.

Kind of like how Lemmy made up communities? Lol you don’t call microblogs “toots” either. Seems every fediverse software has their own terminology.

Also it’s dev, singular. Kbin has been put together by only one dev. I personally find that damn impressive considering it’s functionally on par with Lemmy being only 2 months old to Lemmy’s 4 years.

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

I think they actually have the largest independent index outside of Google/Bing right now.

Others that exclusively use their own index are:

Mojeek (results aren’t great)
Kagi (result are pretty good imo)

I understand your idea, but I think it would defeat the purpose of the fediverse. It would create single points of failure that are un-correctable.

I also think many people forget that Reddit never functioned any differently. Everyone seems to have forgotten (and I’m not saying you have!) that there are and were always multiple subreddits for any given topic. With slightly differing names. The only reason people are forgetting this is because eventually one or a handful became pre-eminent and the others died or became transformed into something more niche.

I think it’s a problem that will ultimately correct itself, but I think a tags based system, like hashtags in Mastodon, would be a better solution for tying communities/magazines together through metadata.

I think it’s a fair point. They won’t be able to remain federated to many instances if their point of contention is open-enrollment.

I understand needing the Lemmy moderation tools to improve and that it’s temporary, but the damage to their own communities and users may not be temporary.

Their users will turn inward and end up preferring their own communities—which is fine. However it also means that non-beehaw users will shy away from those communities in favour of others, lest their home site get de-federated at some point for the same reasons. These effects combined means slow-to-grow, low-visibility communities in the fediverse, and increases the chance that their communities may dwindle if others of the same subject become pre-eminent outside of Beehaw.

In short, while I understand their reasons, I think that it risks making Beehaw.org permanently insular and ultimately much more similar to a non-fediverse website.

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.

This must be a Lemmy thing right? I haven’t experienced this at all on kbin.

That’s makes sense but from an engineering standpoint, anything below operating temp and pressure fundamentally causes more wear.

It may be minimised with configurations such as you describe, but it’s still more wear than if the engine hadn’t stopped in the first place.

How much, I don’t know, but over the course of hundreds of thousands of miles and thousands of stop-start cycles, it adds up.

Well I think I can answer that. It is more efficient for fuel consumption. They all have the systems because it allows them to hit better EPA fuel economy numbers. But better fuel consumption doesn’t mean there’s no effect on the engine.

I’m not saying I’m 100% correct btw, I’m waiting for a mechanical engineer to explain why I’m wrong. But my limited understanding hasn’t found an answer for my concerns yet.

That might be true, I’m not a mechanical engineer but despite that, my understanding is that within the engine block itself, cylinders are primarily lubricated via the system holding pressure. This pressure starts to drop the second the engine ceases.

You can notice the effect on cars that have realtime oil temp monitors. Mine does, and it’s digital. My stable oil temp is around 216 degrees Fahrenheit. After a start-stop cycle, even for only 5-10 seconds or so, the temp drops about 5-8 degrees. After a minute, the temp is down 25 degrees. That’s significant. Essentially the engine is no longer “at temp” for the first 30 seconds or so after it resumes. That’s 30 seconds of additional semi-cold, under pressure wear each cycle.

Thank you, I think you’re right! I misread it for sure.

Small correction. Kbin is not a Lemmy instance. It’s an entirely different backend on the ActivityPub protocol. It federates with “threaded” fediverse sites like Lemmy, and with microblogging sites like Mastodon. Users on kbin can create and interact with both kinds of posts and kbin magazines “Lemmy communities” can natively include both.

Edit: sorry @atypicaloddity I totally misread your comment. Ignore me!