Give it a thumbs up so we know what to prioritize 😊

I’ve been focusing on the backend and federation stuff. But I promise that we will implement it this year :)

Please have a look at the smaller mbin instances as well. It is not good to have one massive server and a lot of tiny ones. Kbin.social is the best example of it, the second best is lemmy.world which just has issues because of its size…

We do not have a “project fund” or something like that. Some of us have donation sites to keep the servers running:

• mine: https://liberapay.com/BentiGorlich
• @debounced@kbin.run https://kbin.run/about
• @melroy@kbin.melroy.org https://melroy.org/thanks.html

My opinion: I do not want to get paid to develop mbin. That creates an obligation and turns it into something like a job. I already have a job and intend to keep it, additionally I don’t want to take the fun out of developing mbin. To commit to it full time or apply for grants or anything would currently be a big mistake I think

Oh that would be interesting as well. I will do that. Checking back in 2h :D

You cloud give mbin a try its developers are nice people :) Although there is only one app for it (interstellar)

The same can be said about gmail and it is the same kind of problem here. Yes lemmy.world is not a profit orient it giant, but it is still a problem when one actor has this power over a federated network. (the scale of the problem is of course a lot larger with gmail)

Mbin isn’t making any drastic changes

UI wise, that one is definitely true

and relying mostly on Kbin’s existing code as its base

This one most certainly not. We actually stopped porting kbin code a few months into the project, because it just was too much work and it was obvious that Ernest didn’t want us to. So everything which changed on mbin in the about 8-10 months since, was purely our own work. Of course the basis will always be kbin, but the form will most likely change

We’ve been keeping the UI mostly as is, because we all like it, however on the backend site of it a lot has changed. The biggest problems kbin had were compatibility wise (federation) and scaling wise. These were the points where we made huge changes. The federation compatibility has improved a lot (yes there is still a lot to do) and scaling/performance has also improved a ton.

The biggest UI changes we made are:

• new filter designs that work for threads as well as microblogs
• a subscription panel
• a usable instance wide modlog
• a cake day display
• and more stuff that I am forgetting at the moment (it’s been a while since I looked at kbin and I am mostly a backend dev)

The backend changes we improved are (imo) more impactful:

• (next release) direct messages are federating
• (next release) pins federate
• deleting users federate
• magazine descriptions are federating correctly
• mods federate
• reports federate
• incoming likes are working
• the “hot” sort actually makes sense with lemmy content because it also looks at upvotes and not just at boosts
• completely redone the hashtag system so it scales at all
• completely redone the background worker system so it scales better (partly next release)

And these are only the changes I could think of in 5 minutes. We likely changed a lot more things, which I just forgot.

My guess is that they just needed to have their own community for a lot of stuff because so many instances are defederated from them. Though I am not sure…

Ich finde es schön. Mangel an Beweise - “Den Medien sind 11,5 Millionen Dokumente zugespielt worden” 😂

And here the diagram by community subscriber count: