Is the kbin project completely dead?

the repo has nothing going on

the kbin.social website partly loads with error

did it just evaporate? or what?

  • originalucifer@moist.catsweat.com
    126·
    8 months ago

    the original developer mentioned handing off the site/project to other people due to personal issues but that was like a month ago.

    this is part of the reason it was forked to mbin. the risk of a project being managed by a single person instead of a community is very real.

    it seems dead, but i like to remember there would be no mbin without kbin

    • wildncrazyguy138@fedia.io
      14·
      8 months ago

      True that, I just took a look at the FAQ and it still references kbin.

      Question, how do we donate to this project?

      • BentiGorlich@gehirneimer.de
        20·
        8 months ago

        We do not have a “project fund” or something like that. Some of us have donation sites to keep the servers running:

        My opinion: I do not want to get paid to develop mbin. That creates an obligation and turns it into something like a job. I already have a job and intend to keep it, additionally I don’t want to take the fun out of developing mbin. To commit to it full time or apply for grants or anything would currently be a big mistake I think

        • Ludrol@szmer.infoEnglish
          8·
          8 months ago

          I do not want to get paid to develop mbin.

          In couple of years you will burn out doing this for free. Not getting paid opens up the project for another Jia Tan to come along and smuggle malware.

          There was recent talk by Rockstar Programmer Dylan Beattie that highlighted this problem. His website https://freeasinweekend.org/ and YT talk https://www.youtube.com/watch?v=vzYqxo13I1U

          You don’t need to go 100% job or 100% mbin. You could theoretically go for less hours (like Fridays off) to work on mbin.

          • BentiGorlich@gehirneimer.de
            10·
            8 months ago

            Maybe in the future. Currently so few people are using mbin that I doubt it would be any substantial amount. It also creates a lot more work when doing your taxes. So yeah if mbin gets a user base like lemmy currently has this would be another story. But it does not and it does not look like we will be there any time soon

      • jwr1@kbin.earth
        12·
        8 months ago

        I don’t think there is a way to donate (monetarily) directly to Mbin, at least not at the moment.

        The second best thing might would be to donate to server admins, which a lot of them actually are Mbin developers anyway.

  • Chozo@fedia.io
    55·
    8 months ago

    Ernest, the lead dev for Kbin, has had a lot of big events happen in his life recently, so he has a tendency to just kinda disappear for weeks/months at a time while the project gets put on hold. He’ll usually come back, announce new plans for development, maybe push out a few updates, and then inevitably go radio silent again.

    I believe he’s got a few people assisting him now, but development has definitely slowed to the point of becoming concerning. I think it might be time for the Mbin team to start getting a little more free with the fork.

      • Chozo@fedia.io
        30·
        8 months ago

        I believe that currently, Mbin isn’t making any drastic changes, and relying mostly on Kbin’s existing code as its base. As far as I’m aware, the Mbin team are mostly just doing maintenance-level development; fixing things as they break and making optimizations, but not so much in the way of developing new features. Mbin is currently just basically a copy of Kbin, without much distinguishing the two.

        Since Kbin doesn’t seem to be moving much at all, I think it might be a good idea for Mbin to start flexing their own muscles a bit, and making it into its own separate project. Otherwise, having a copy of a stale project just leaves you with two stale projects.

        • BentiGorlich@gehirneimer.de
          22·
          8 months ago

          Mbin isn’t making any drastic changes

          UI wise, that one is definitely true

          and relying mostly on Kbin’s existing code as its base

          This one most certainly not. We actually stopped porting kbin code a few months into the project, because it just was too much work and it was obvious that Ernest didn’t want us to. So everything which changed on mbin in the about 8-10 months since, was purely our own work. Of course the basis will always be kbin, but the form will most likely change

          We’ve been keeping the UI mostly as is, because we all like it, however on the backend site of it a lot has changed. The biggest problems kbin had were compatibility wise (federation) and scaling wise. These were the points where we made huge changes. The federation compatibility has improved a lot (yes there is still a lot to do) and scaling/performance has also improved a ton.

          The biggest UI changes we made are:

          • new filter designs that work for threads as well as microblogs
          • a subscription panel
          • a usable instance wide modlog
          • a cake day display
          • and more stuff that I am forgetting at the moment (it’s been a while since I looked at kbin and I am mostly a backend dev)

          The backend changes we improved are (imo) more impactful:

          • (next release) direct messages are federating
          • (next release) pins federate
          • deleting users federate
          • magazine descriptions are federating correctly
          • mods federate
          • reports federate
          • incoming likes are working
          • the “hot” sort actually makes sense with lemmy content because it also looks at upvotes and not just at boosts
          • completely redone the hashtag system so it scales at all
          • completely redone the background worker system so it scales better (partly next release)

          And these are only the changes I could think of in 5 minutes. We likely changed a lot more things, which I just forgot.

        • originalucifer@moist.catsweat.com
          19·
          8 months ago

          youre not wrong, they spent a lot of time refactoring things, and still are.

          that said, the list of changes in the last several versions is very long, and the code base is no longer trivially similar. looking through the waiting prs, there are a lot of interesting bits like extending microblog AP connectivity (tag handling).

          the mbin guys have been pumping out releases steadily since the fork, including implementing managed documentation and version numbering. it has well exceeded kbin at this stage.

          theyre prepping for a 1.7 release soon. when was the last kbin update? to me, theres only one stale project here.

          • Chozo@fedia.io
            8·
            8 months ago

            Thanks for the insight! I’m not super familiar with how the development cycle goes, so my thoughts are coming from the standpoint of a user experiencing both platforms. I’m sure that a lot of the back-end stuff has probably had a lot of improvements, but the end-user experience between Kbin and Mbin are still largely identical, I feel.

            I was gonna load up Kbin to try to do a live comparison but, uh… Yeah, who knows when that’ll be possible again lol

    • cum@lemmy.cafeEnglish
      4·
      8 months ago

      So it basically failed the bus factor

      Hopefully mbin becomes more resilient, or if Lemmy just gets some nice rewrites.

    • RedSquadCampFollower@lemmy.worldOPEnglish
      1·
      8 months ago

      it might be time for the Mbin team to start getting a little more free with the fork.

      the impression i had of mbin was very “anything goes” did that not end up being how things shaped up??

      • originalucifer@moist.catsweat.com
        10·
        8 months ago

        its a community. anyone can generate a pr, code it up and it gets discussed. so far there has been no crazy drama about what to include or not… no one has proffered any incompatible ideas. its been quite pleasant

        its all public though, in the matrix or github channels

      • BentiGorlich@gehirneimer.de
        6·
        8 months ago

        That was the message that was pushed out when @[email protected] started the fork, because a lot of people were not particularly fond of the way he did it. We were trash talked a lot in the first months and obviously (and sadly) that kinda stuck on a lot of people.