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.

And I can see this comment from kbin, so seems to work this direction too.

though kbin still doesn't render the code block correctly it seems

Yeah, I hope ernest (or someone else) fixes it soon. Mbin has fixed it, so it should be possible to check there how it was done.

I did make a frontend fix for it which is included in KES and available standalone on Greasyfork. But it would be much preferable if this was fixed in kbin itself.

I think the big problem is that the issue on codeberg is closed. Ernest never got involved, but other maintainers closed it as a "lemmy issue" which it isn't. Lemmy is federating completely legal HTML with escaping applied to spec and kbin should be able to understand it. Mbin can understand it.

It it like he can see us but we can’t see him?

Opposite way around. We can see him but he can't see us.

The reason you can't see him is because you're on Lemmy which will only display microblog posts if they're (1) a reply to a Lemmy post, (2) made from kbin/mbin, or (3) replied to by someone from kbin/mbin (not entirely sure about this one).

To newly federate a magazine with Lemmy, search for it using the syntax !Polytopia@kbin.social in Lemmy's built-in search. This worked for me instantly when I just tested it on lemm.ee, after confirming that it 404s before doing it.

On Lemmy, users can send each others direct messages. It seems like Kbin/Mbin has no way of displaying those direct messages. Is that correct or is there a way to show direct messages?

Direct messages exist on kbin/mbin, but users are currently unable to send or receive them from other instances than their own. Sending is implemented but intentionally disabled by ernest, for unknown reason, but it might have to do with receiving not working.

Mbin has an open issue on this and yesterday someone said it's planned but low priority. It also links to the related kbin issue.

From what I can tell, it's mostly brought up in the discussion of a pull request for supporting federated dislikes.

That's where I originally saw it. I'm sure there's probably some more discussion on matrix though, that seems to be their main discussion platform.

Some additional links without discussions:

• The commit that removes the public downvotes
• The associated pull request

Edit: Also, to clarify, it's only seeing who downvoted that's made private, the actual amount of downvotes is kept public. It's not a Youtube situation.

Having thought about this for a bit, I think it might actually be better for ernest if this instance died a bit. Not entirely, but it could use some redistribution of users to other instances.

Like, it wasn't meant to be this big main instance of kbin. That's just what it became. And it's got to have an effect on his stress levels and development time.

I feel like the instance is like a ballon that continually gets pumped with fresh air. Ernest constantly has to make sure the balloon doesn't pop. Maybe it would be better for it to pop so he can focus on other things?

I was considering moving to mbin, but their decision to make downvoting private makes that a very unpleasant idea for me. Public voting was one of the initial selling points for kbin for me. If I move, then it's probably to another kbin instance like kbin.earth for now.

I appreciate that earnest made a post yesterday, or maybe it was the day before, saying that he is not dead and hasn't given up on kbin. It's not on this magazine, so I'm not sure where it was since this seems to be the most appropriate one, but in any case.

Are you not talking about this thread?

and invite other moderators

Definitely. I've applied to a handful of magazines weeks ago and have read about others having done so too. I really think magazine ownership requests should be accepted automatically on kbin.social. There's already requirements in place to whether you can make one, that should be good enough for abuse safety measures.

Instance moderators would be better, but I don't know if there's people lining up for that role whom he also can trust with it.

and contributors.

The issue here is that all contributors have moved on to mbin. You don't just look for contributors, the contributors choose to contribute. So unless he's willing to pay them, I don't think this is a problem he can solve, and I doubt he makes enough money to hire people.

I know. I'm just saying that the idea people would magically help out on kbin if he was more open about his plans doesn't work out, because the people willing to do so would either already be contributing to cleaning up the backlog or have moved on to mbin.

Btw, do mbin devs look at kbin issues too or do common problems have to be posted to both repositories to be seen?

@ajsadauskas I think Github's awesome lists are kind of like this. They're human-maintained catalogues of worthwhile websites on a specific topic.

I'm just focusing on clearing spam

This is good to hear, but there's still soooo much spam on the instance, it's clearly too much for you. Can you please accept some of the magazine ownership requests (and moderator requests on your magazines) so we can actually help you with this? I know I've applied to a few, which are still pending, so there's definitely people waiting in line.

Make sure to actually mention him if you want this to be seen. @ernest

On the other hand, if people really wanted to contribute, there's plenty of open issues on Codeberg that are unadressed. I agree that it would be better to announce plans in advance rather than surprise drop them, but I doubt there would be more contributions from the community.

I assume ownership requests need to be manually approved by ernest, right? I've tried applying to some (not ernest-managed ones) weeks ago because of spam on them and nothing happened yet.

Twitter has taught me that nowadays people are too adaptable, 90% of people will stick with Reddit no matter what they do.