It’s a new year — about 6 months since that Reddit migration occurred — and Kbin progressed a ton in 2023. What are your thoughts on it? How much value have you gotten out of it, and what would you like to see in the future?

  • ThatOneKirbyMain2568@kbin.socialOP
    link
    fedilink
    arrow-up
    4
    ·
    11 months ago

    It’s nice to see more Kbin and Mbin instances popping up. I’d love to get to the point where the majority of Kbin users aren’t on one instance, though that’s probably a long while away.

    • originalucifer@moist.catsweat.com
      link
      fedilink
      arrow-up
      3
      ·
      11 months ago

      i think part of the issue is the conflation of instance branding/application name. i wish they were a bit more distinct.

      external ‘kbin’ users would be any federating platform, in this context. kbin.social users are that, @kbin.social

      for example, if someone was running kbin.nonsense.com and wanted to change to mbin, they would be stuck with the kbin branding.

      the site branding should be somewhat agnostic to the underlying application (in my opinion, of course).

      • ThatOneKirbyMain2568@kbin.socialOP
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        I see where you’re coming from, though having the instance be related to the underlying software helps a lot with clarity. I still have trouble remembering whether programming.dev is a Lemmy or Mastodon instance, whereas lemmy.ca causes no such issues.

        Also, with Kbin and Mbin, I don’t think it’s much of an issue. Kbin.run uses Mbin, and I’ve never seen that as odd. The differences between the two aren’t very significant anyway (i.e., it’s clear that they’re both versions of the same general thing). I could see it being a problem if you wanted to switch your instance from Kbin to Lemmy, but that seems like an unlikely scenario that isn’t worth the sacrifice in clarity.