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
Honest question: what’s the reason to make a fork instead of contributing do kbin itself?
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.
deleted by creator
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.
That makes sense!
For my basic knowledge working side by side with a lot of devs, I totally agree with the way Ernest thinks. It’s essential for a product that’s growing up to have a solid core that will not need to be rewrote in the near future.
But also, as an user, I keep wishing we could see more features, like the API for mobile apps.
I mean, besides what Ernest and Melroy thinks that’s the right way, there’s also what the users need, what the users want and what the project needs to escalate (new features vs core rewriting). And probably there’s not a right answer for that.
Yeah, I think it became a bit of an impossible solution the second Ernest’s proof of concept suddenly attracted a whole bunch of users and attention after the Reddit exodus. Kbin was clearly not ready, and I admire him for staying on course with the development after that despite pressures.
That said, users are not wrong to want easy to implement features asap. So I personally think the fork makes a lot of sense, though everyone could do without the occasional bad faith from some of the people involved.
What happened to Lbin?
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.
I mean, everyone’s using activity pub protocol tho. I think when activity pub starts getting fragmented is when it’s time to worry.
Yeah, this is what I was about to write. As long as they can all talk to each other, who cares? They used to be like a dozen popular email clients. It didn’t really create any issues (for the end user at least)
The issue is quality. 2 mediocre platforms is worse than 1 decent platform.
Over on mastodon, for example, there’s official mastodon … and then there’s a few forks of mastodon (eg glitch and hometown), pleroma and its fork akkoma, misskey and its forks sharkey, and firefish, and then forks of firefish, iceshrimp and catodon.
And yet there’s a good amount of conversation about how more platform diversity is needed to compete with mastodon. None of the above mentioned alternatives are especially stable, or perceived to be stable (firefish for instance was very popular in 2023 but has literally burnt to the ground with the main dev just abandoning it and the main instance), and so instance admins tend to be wary about running them and so they don’t get popular.
If half of the devs working on alternatives just banded together to make a compelling and stable and committed “alternative”, the fediverse would be in a better position.
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.
Presuming your story is true (I don’t know either way) … yes, a place the fediverse attracts that kind of behaviour (as well as a few others that just aren’t worth getting caught up in and relying on). And starting a fork is, unfortunately (as forks can be awesome things), a tell-tail sign.
Many are inclined to mock of be unhappy about how seriously the head of Mastodon takes himself (and how dominant his platform is) — he calls him the CEO of mastoodn, it’s actually a registered non-profit company, he openly considers himself the BDFL (beneficent dictator for life) — but he’s been at it since 2016, is committed, creates an appearance of stability and is the only one that’s got the whole fediverse thing working on a significant scale, whatever flaws he and his project might have. All of the hacking culture and sentiment can only take a project so far … as it ultimately needs people and users to be successful.
Then its great he has his own Fediverse with hookers and blackjack.
What are the key differences? How is it more open?
kbin had not been accepting some commits and apparently were moving quite slowly with newer features. So, this is more like a dev version type implementation. It is more “open” to changes and commits apparently. Not more “open” as in open-source.
I don’t get the pull request part. does that mean each instance does not control who they federate with???
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).
It’s git terminology which boils down to that anyone can contribute to the source code if the community approves the changes made.
thanks
That just refers to the source code. How instances operate is a separate thing.
oh that makes sense. I was worried for a min.
