I’m out of the loop.

  • concrete_baby@sh.itjust.works
    link
    fedilink
    arrow-up
    15
    ·
    1 year ago

    Lemmy and kbin are two different forum software that can be installed and run on servers. Because both use the ActivityPub protocol, the content between them can be shared. So, a Lemmy user will be able to see content from a server running kbin, using Lemmy.

    • rist097@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      But how can I see kbin content from lemmy, I couldnt find an option yet. Also from kbin I cannot find lemmy communities

      • Communist@beehaw.org
        link
        fedilink
        arrow-up
        18
        ·
        1 year ago

        There isn’t an option, you can’t even tell but you already have the kbin content.

        You can’t disable it.

        The reason that’s happening right now is because kbin is enacting ddos protection using cloudflare so they aren’t federating properly, this is a temporary problem.

        • shadowtux@fedia.io
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Is this only some kbin instances thing or all kbin instances thing? I’m fairly sure that fedia.io (/kbin instance) does not use cloudflare. But that would definitely explain why I’m struggling to search some instances that might use it.

              • Yozul@beehaw.org
                link
                fedilink
                arrow-up
                4
                ·
                1 year ago

                kbin being more centralized is just an unfortunate accident of timing. I was only first publicly released two months ago, and from what I understand there’s still not much help available for starting up a new instance of your own, and the lone developer over there has been busy trying not to let the kbin.social server catch fire.

      • tiwenty@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        This is due to Kbin using Cloudflare anti DDoS, which disallows Lemmy instances reaching it

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

        To see Lemmy content on kbin, just add the full address of the Lemmy instance to the end of the kbin URL. For example, https://kbin.social/m/lemmyworld@lemmy.world lets you see content from @lemmyworld@lemmy.world on https://kbin.social.

        The other way round should also work (ie. to see kbin content on Lemmy), but for some reason it’s not working on major Lemmy instances for me, even though they are federated to kbin.social and other kbin instances.

      • danisth@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Same here. I can actually see the Kbin communities when I search, but it is showing no content. Not sure what it looks like from the Kbin side.

        • Outfield7687@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          1 year ago

          As another poster said, CloudFlare protection is breaking sync with Kbin at the moment.

          I set up an account in kbin last week and objectively prefer it, but it’s become kind of unusable over the last couple of days.

        • Yoshizuki@fedia.io
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          It looks good :-)
          The cloudfare wall is a bit annoying but the UX is great. I didn’t try any Lemmy instance though…

      • headingtofall@lemmy.world
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        The main kbin instance, kbin.social is getting slammed and cloudflare is breaking their sync in both directions, so currently you can’t see their content on any other Lemmy or kbin instance afaik, and you can’t see Lemmy content on there. Hopefully that gets fixed soon but it’ll probably take a while. The other kbin instance are tiny and don’t have much content but I think should be visible here