SpacemanSpiff

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.

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.

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.

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.