Pamasich

We don’t really know. Supposedly it is, ernest just isn’t pushing the code to codeberg, instead keeping it locally. He has mentioned before he’s going to push the latest changes (though he never did that), so it sounds like there do exist changes not reflected on the repository yet. But I have no idea how things went since then.

I believe mbin stopped merging kbin changes, probably either when they had their fallout with ernest where he pushed unfinished code that caused issues, or when he started his refactoring which I’ve seen some mbin contributors dislike because it requires changes on their side too.

Either way, there’s definitely features missing on mbin that I know are in the kbin source, like the sort options on profiles. Collections are definitely there too.

when in theory they all use 0.10.1

First of all, there’s no way this is true for mbin. It’s a fork, it has its own versions.
Fedidb says most instances of mbin (on its first page of instances) use version 1.5.3, though kbin.melroy.org uses 1.6.0.

But also, hasn’t kbin been 0.10.1 since forever even before ernest added all the new features? I don’t think that version string means much if anything.

That’s why I use Copilot.

Asked it for the official documentation, got a link to the /current/ documentation’s chapter on operators. Then asked for the heading about the IN operator and it gave me all four of the numbers. No need to wade through outdated or irrelevant results.

I understand why they disabled public downvotes (since they’re accepting incoming ones now, they don’t want to expose everyone’s downvotes from other instances), and I remember they gave some reasoning on Github for why it makes sense to not hide upvotes too, but do we really need incoming downvotes? I think that feature should be a toggle where you either have downvotes hidden but federated, or visible but not federated. And then the instance owner can decide what they prefer.

That’s really my main issue with mbin. While I’ve gotten too used to the All Content view and collections, both of those are on their roadmap, so they’ll be coming eventually.

ChatGPT is going to get you rejected for made up sources for sure.

I got a response from them on Reddit:

We didn’t know which platform would take off, and we were nervous that because Kbin and Lemmy are so similar one platform might shut down in some sort of consolidation down the road. Also when we made them, each had very serious drawbacks for our media (Lemmy needs a lot of clicking to access the media, while kbin turned any media that wasn’t in a 3:4 aspect ratio into a funhouse mirror.) So each of us took a community and somewhere down the line we’ll re-evaluate.