kbin.earth meta

My instance rimworld.gallery has been stable ever since mbin was introduced. Sure, it was a bit of a bumpy ride in the beginning, but now it will run for weeks without any trouble. Handling about 100 real visits per day and 1000s through federation, serving big jpgs 5-34MB continuously without a hiccup

Long story short; we are doing our best :). Mbin development team is still small. But I like to focus on stability a lot in the recent years, and I still am.

Progress is maybe slow but steady, introducing missing features and performance improvements along the way. Maybe it's good to mention that all developers on Mbin work voluntarily without getting paid. Lemmy developers on the other hand are fully paid by their community and can work full-time on Lemmy. We all do the work next to our main job. Thank you for your understanding.

I'm not an admin, so I'm not qualified to answer that part, but I also came from kbin.social originally. I moved to fedia.io/Mbin when kbin.social and kbin itself died. I've definitely had a much better time on Fedia/Mbin as far as stability. I think that probably comes down to several factors:

• the stability of the software itself
• an attentive admin who's around to kick the tires
• less load on the server/s

For comparison, here's the last successful capture archive.org made of the kbin.social stats page. It lists 64601 users and 115388 threads. Here's the present-day fedia.io stats page which as I write this comment is reporting 5132 users and 9629 threads. Naively extrapolating from these figures, kbin.social was apparently taking >10 times the load that the largest Mbin server is currently. On the one hand, it would be nice to see Mbin grow to the heights of early kbin, but the current situation is far more manageable for these mostly out of pocket/donation-supported projects.

i think the stats over at https://mbin.fediverse.observer/list speak for themselves.. coming up on the 2 year mark for the top servers with general uptime over 97%. that seems longer and better than kbin ever achieved.

the devs have fixed a huge number of internal issues left over from kbin, and added a ton of features.

one thing we do need as a platform is more users. more users will require admins to thoughtfully construct scaling methods and highlight pain points that might need addressing in code.

running one of these, most of my issues are with latency due to my own self-imposed resource constraints. its pretty solid from my point of view. i cant remember the last time something (service or database issue) took the server/site down. the tech support from the dev team is great.

i spend most of my time contemplating the next scaling steps to allow for more users whereas last year it was more about getting the server stable.

I feel like it's been pretty stable, especially now that there are more developers working on it through Mbin. I've been running kbin.earth for over a year and the Mbin developers have been very helpful in resolving any issues I (and other admins) have come across.

Honestly, the worst thing that's happened to Mbin was the kbin.run instance suddenly shuting down and the admin/developer disappearing out of nowhere, but that could easily happen to any Fediverse instance (Mbin, Lemmy, Mastodon, the software doesn't matter). And, that was way better than what happened to kbin and kbin.social, where the admin and solo developer went silent, causing kbin itself to dwindle out.

All that to say, Mbin learned from Kbin's failures and focused on having a group of developers instead of just one main developer (which caused a single point of failure). So, yes, I would indeed consider Mbin stable; just pick a server you believe would stick around for a while, and hopefully, if a server does ever need to shut down, they would at least give a warning in advance (I know I would).