So my understanding is that KBin.social is now gone from the internet for the indefinite future. Ernest, who meant well, simply could not keep up with the demands due to his personal life and the development issues that were cropping up all the time. Let me get ahead of any replies and say that it’s perfectly reasonable to shut down a large instance if it’s taking up your time and money or becoming a burden on your personal life. Personal health should always come before a bunch of random dudes/dudettes that happen to be on the internet. Additionally, it’s a good reminder that developing software while also maintaining a large instance probably isn’t a good idea and that you should probably make sure you’re taking a reasonable amount of work off your plate.

But I can’t help but feel like there’s another story here regarding the potential risks of the fediverse: Admins need to be ready to migrate ownership to others who are willing to take on the financial or user account management burden. Additionally, there should be a larger focus on community migration features for more flexibility to sudden instance losses.

I managed a community that had partially migrated to Kbin after the great reddit exodus last year and managed to continue to admin said community up until a few months ago when Kbin’s service became very very spotty. I understood Ernests’ particular dilemma so I was willing to give it a month or two to figure out what actions I needed to take to migrate the community again, but enough time has passed now that I am no longer confident that Kbin will return to even a read-only, moderator only state. This means that whatever community I had there is now completely out of my control and the users might not know why posts have stopped entirely. Basically, I have to start from the ground up which might be OK but I’m not particularly keen to start it all over right now.

So this is basically a plea to the admins out there: If you are having trouble with management and need to stop, could you please give the community a vocal heads up so that whatever subcommunity happens to form on your site has some means of migrating? Additionally, software out there should have more policies for community migration, whether that’s lemmy or mbin, as we never know when it might be necessary to migrate to a new domain under different ownership. Lastly, if there’s an option to give ownership to others in the community, please consider it as it would really help the fediverse if admins were willing to migrate domain and databases to other users who are willing to carry the torch.

That’s it from me for now, thanks for reading this minor rant. 🤙

  • Chozo@fedia.io
    link
    fedilink
    arrow-up
    67
    ·
    5 months ago

    Kbin is dead. Long live Kbin.

    For those who enjoyed the Kbin experience, Fedia.io has been fantastic! It’s running Mbin, a fork of Ernest’s Kbin. It’s stable and online reliably!

    Hopefully Ernest is able to take care of himself. I’ve only ever had limited interactions with him, but he seems like a good guy, and I hope he’s able to get back to work on fulfilling his vision for the project.

    • BentiGorlich@gehirneimer.de
      link
      fedilink
      arrow-up
      15
      ·
      4 months ago

      Please have a look at the smaller mbin instances as well. It is not good to have one massive server and a lot of tiny ones. Kbin.social is the best example of it, the second best is lemmy.world which just has issues because of its size…

      • ReveredOxygen@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 months ago

        My understanding is that mbin encourages microblogging to !random, which you can’t see from other instances. Is that incorrect? If that’s the case, I really don’t understand how mbin federation is supposed to work

        • BentiGorlich@gehirneimer.de
          link
          fedilink
          arrow-up
          3
          ·
          4 months ago

          The microblog side works the same as mastodon: following people. You cannot follow random from other instances, because it would creates way too much traffic on larger instances. Imho there should be no random magazine. It only exists for things that cannot be assigned a magazine, because it is not possible to post something without a magazine. We inherited that from kbin

          • ReveredOxygen@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            4 months ago

            But on mastodon, there’s a feed that lets you view all posts from all federated instances. Wouldn’t mbin users be excluded from that feed when posting to !random?

            Edit: I was looking, and it seems to me that if a user posts to !random, I can’t even see it on their profile from mastodon? Am I misunderstanding this?

            • BentiGorlich@gehirneimer.de
              link
              fedilink
              arrow-up
              3
              ·
              4 months ago

              That is a very good point 🤔 I just checked the code. Your “subscribed” feed does include the users you follow as well, not just the magazines

              • ReveredOxygen@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                4
                ·
                4 months ago

                Actually, it seems I was misunderstanding. Apparently all mastodon posts get federated as appearing on !random, so I’m not sure what I was seeing

                • BentiGorlich@gehirneimer.de
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  4 months ago

                  That is right. When you do not explicitly tag a magazine from mastodon (or a hashtag that is matched to a magazine) then the post ends up in the random mag