Mbin is a decentralized content aggregator, voting, discussion and microblogging platform running on the fediverse network. It can communicate with many other ActivityPub services, including Kbin, Mastodon, Lemmy, Pleroma, Peertube. It is an open source alternative to other link aggregator services like Reddit. The initiative aims to promote a free and open internet.
Mbin is focused on what the community wants, pull requests can be merged by any repo owner (with merge rights in GitHub). Discussions take place on Matrix then consensus has to be reached by the community. If approved by the community, only one approval on the PR is required by one of the Mbin maintainers. It’s built entirely on trust.
It seems it’s claim to fame is being more open and accepting of community changes and improvements. It can install as either bare metal/VM or as a Docker container.
Although anyone can install it and self-host it, their project page also contains a link to various instances that already exist and which anyone can register on.
See https://github.com/MbinOrg/mbin
#technology #opensource #Fediverse #linkaggregator #decentralised
One great instance of Mbin I’ve been on is kbin.run. So far, very stable and no complaints
Feel like the *bin and the *key have a lot of cool features, but way too many forks to have a understandable product. It’s pitty
It’s one of my main concerns with the fediverse, that tech people’s (and people generally) inclination to not work together and instead do their own thing will be detrimental on the whole.
Which is EXACTLY this. Melroy(Mbin dev), was a Lemmy dev that was “ignored”, then he was a kbin dev who was… “ignored”. But then he ran his own instance, which was again, ignored. So then he started Mbin, which of course he named after himself(Melroy Bin). In between each of these attempts, he’d go to numerous communities and post long rants trying to call out the other devs about how terrible everyone else was and how no one is listening to his brilliance and he’s the One True Savior of the fediverse.
Dude is pathologically egotistical and is exactly the kind of person I don’t want admining anything.
Honest question: what’s the reason to make a fork instead of contributing do kbin itself?
Saw somewhere it was said the kbin side was going too slowly and not accepting some commits that their community gave. Some wanted to move quicker with newer features and enhancements.
My understanding of the situation is that Ernest, the main developer behind Kbin, thinks of the current Kbin as a proof of concept, and he is doing profound rewriting of the codebase to better fit his vision of how it should be working.
Meanwhile, other people wanted to contribute to Kevin directly, developing a better product on top of what Ernest considers to be too shaky foundations. So he’s not all that interested in pursuing that part of the development before he is happy with the core.
This also leads to a dynamic where he still has his own vision for the project and it goes through him, whereas other contributors want to make it their own more and develop something different.
It’s hard to see how to make everyone happy here without forking. Hopefully both projects can still gain from each other in the future: Mbin can benefit from the rewritten codebase of Kbin, and Kbin can implement features from Mbin after seeing that they are good and work well. In either case, the continued development as separate projects is probably not all that bad.
Melroy, lead dev, is the kind of person that if you don’t take his “advice”, he goes “fine, my way or the highway!”. He used to be a part of Lemmy dev supposedly. Then he was part of kbin dev. Then he tried to just make his own instance. Then when that didn’t work he started Mbin(which, if you haven’t realized, is named after him - Melroy Bin). Dude is pathologically egotistical.
I don’t get the pull request part. does that mean each instance does not control who they federate with???
That just refers to the source code. How instances operate is a separate thing.
oh that makes sense. I was worried for a min.
No, the pull requests are to do with submissions of source code to the core project. The project owner has to review and accept those changes for them to happen (or not).
