I know some of you consider this as documented whining. I hear you but won’t stop sharing my opinion and reminding. I recommend continuing commenting on the original post to keep it a bit organized (this post is a link to it)

Update: this thread has gotten out of hand. This is not what I intended, this is not what anybody should want. Let’s leave it at this, for now.

  • mozz@mbin.grits.dev
    link
    fedilink
    arrow-up
    24
    ·
    edit-2
    5 months ago

    I’m extremely in favor of being able to interact with both Lemmy people and Mastodon people, and I wanted to switch to kbin because it seems like one of a very few solutions that can do that.

    Initially I was pretty skeptical of mbin, because as a general rule the “screw the existing maintainers let’s fork” people are usually mistaken about some things, but I have to say having installed and worked with both, I like mbin significantly better. My experience is minimal, and the fork was pretty recent, but mbin fixes some specific things that I had trouble with or that irked me during the short time I was working with kbin. Some significant instances also seem like they’ve switched over to mbin. Having kbin’s “flagship” instance down for like a week didn’t really help either. As I understand it, the mbin philosophy is “let’s fix up the backend and get federation more solid before we do much more in terms of big new features” which I can get behind.

    They’re both very rough and early pieces of software, honestly as is the entire Lemmy side of things it seems to me. If you’re interested because you don’t want things like the 0.19 federation breakage, then I am sad to report that you might find broken stuff in kbin / mbin as well.

    I honestly have no idea about the drama side of things. I wish all good things for Ernest and I’m happy with the software he 99% created. kbin has some things (e.g. combined Lemmy+Mastodon posts all in one home screen) which mbin doesn’t have, which makes it kind of a shame that they’re being developed apparently irrevocably separately at this point. IDK. Like I say I have no idea about that side of things.

    Just my 2c as a person that installed mbin recently and likes it

    (Edit: To answer the specific question, it seems like they’re completely separate at this point. They split in early October with no synchronization in the separate paths of development since then, it looks like to me.)

    • density@kbin.social
      link
      fedilink
      arrow-up
      17
      ·
      5 months ago

      I think this is the most level headed pro-mbin comment I ever read.

      If the project could attract and retain more of this energy it would only be a good thing.

      • mozz@mbin.grits.dev
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        5 months ago

        You’re making me wonder now what weird shit I’ve wandered my way into

        Edit: Welp, I looked into the drama; not enough to really understand it but enough to get a general idea. All I can really say is I want no part of it.

        • density@kbin.social
          link
          fedilink
          arrow-up
          5
          ·
          5 months ago

          Well I’m not involved so don’t let me put you off it. :)

          In broad principal I think a lively kbin fork is desirable.

          It is very strange that the people associated with it spend their time doing posts like this one. No matter what you think of someone development style, tracking their behavior like this is fucking weird. Bordering on harassment. And in service of promoting their platform.

          Why not announce features and bug fixes like a normal project?

          But honestly I am hoping that if some more calm people get mixed up this will cool down.

      • bmzero3@kbin.asdfzdfj.xyz
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        Agreed, I also hope for this to be the case (and tried my besht to facilitate it), but as you can see you could say that mbin’s community building is …not so great right now.