I actually started on Kbin.social, but then it got shut down, Kbin died and now fedia.io seems to be the largest one running MBin. I like the interface on MBin and I guess it’s good to have a diverse fediverse with different services, but at the same time, why use mbin when everyone congregates on lemmy instances? The local magazines on fedia are for the most part, quite dead, when compared to lemmy collections. In the end I feel like there aren’t enough people to go around to support many more services like MBin and Piefed.
At risk of answering a question with a question… Is there a drawback to using mbin? Are there certain ways that it makes interacting with Lemmy awkward or difficult, or is it essentially just another interface? There are lots of frontends for the threadiverse - Lemmy UI is just one.
I know that mbin has additional features on the backend, but is there something you are missing out on?
Just to be clear, mbin is not just another frontend but a completely different software (including the backend side of it). Like Lemmy it uses activitypub to communicate with Lemmy but also with Mastodon.
https://github.com/MbinOrg/mbin There’s a few different instance lists at the bottom if you want to browse around and check the settings and stuff.
Yes, an important point, as I mentioned! However, the question was if there is a reason to use mbin if you are primarily interacting with Lemmy.
My question was if there is any drawback to it. From what I’ve seen (at a purely superficial level) mbin is perfectly capable of taking full advantage of what Lemmy has to offer.
It’s mostly fully compatible to Lemmy. The only minor thing I noticed is that Lemmy edits are not getting federated properly (maybe that’s fixed by now, I just noticed it in some threads in the past).
Federation issues of course can occur, but that can also happen with Lemmy, or activitypub in general. I’ve been pretty happy with it as I prefer the UI just way more.