Learned about this fork from a post about a potential shutdown of Fedia.io, a Kbin instance.

https://lemmy.world/post/6797580

As you can see in the comments, https://kbin.run/ already moved to Mbin.

Interesting to see if that can help with the development of new features compared to kbin being managed mostly by the main developer.

  • thepaperpilot@beehaw.org
    link
    fedilink
    arrow-up
    9
    ·
    1 year ago

    I was looking into hosting a threadiverse app previously and was interested in kbin because lemmy was dealing with the csam stuff at the time and I liked the idea of combining microblogging into the threadiverse app. My overall takeaway from kbin though was that it was too new / missing too many features I needed, and development was slow enough that it felt like I’d have to implement all I need myself. So a community fork of an already not super active repo sounds… Well, I’m not optimistic about it, at least.

    • Blaze@discuss.tchncs.deOP
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      The general issue of Kbin is that most of the development has to be approved by the main contributor of the project.

      This fork is meant to be easier to contribute to. Let’s see how it evolves.