So I did figure out that yes, #Mastodon can federate #Lemmy and #Kbin content. The problem is that Mastodon doesn’t know what to do with it, so it (the group) looks like a user that boosts all posts and comments.

I found myself browsing the “federated group” @selfhosted over on https://kbin.social, as I think Kbin has a nicer UX for it.

I didn’t really want to create a separate account for group stuff, but that might be what we do in the short term. 🤔

    • Eddie@lucitt.social
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Hm, that’s very interesting. I wonder if the platforms will build upon each other with future updates or if they’ll continue to remain “seperate” in terms of formatting and QoL. Very interested in the future of cross platform federation accounts.

      • the_thunder_god@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        @Eddie I know the kbin dev has been adjusting the federated backend to work better with mastodon. So I think it will all get better, it’ll just take time.

        • ThorrJo@lemmy.sdf.org
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          a #Lemmy server requires a fraction of the RAM that a #KBin or Mastodon server does.

          If you want a personal microblogging server, run Pleroma or Akkoma, they are waaaAAAAAY less resource-intensive than Mastodon. Especially after some truly god-awful database queries were fixed in the last few months. (Load on my database server dropped by approximately a factor of 25x!!)

          • Mike Kasprzak 🦖@jammer.socialOP
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            @ThorrJo @selfhosted lol, I can relate to thay 😆. I run an event & website that was notorious for its poor performance at the beginning and end of events. A few years ago, with our servers ready to fall over, I noticed a certain query was hogging the database server’s CPU. I made the tiniest fix to correctly use indexes, and we instantly went from 400% CPU usage to at most 20% (across 4 cores). 😅

            Though it’s been fixed for ~3 years, I still see folks warning others about the slowness. 😅