Vote if you like, but the primary reason I’m posting this is because this community has been linked as a reddit alternative in the post.

Welcome gamers! You do not need an account on kbin.social to post here. Pick any Kbin or Lemmy server (lemmygrad and lemmy.ml are not recommended), make an account, and type @guildwars2@kbin.social in the search bar to get here.

Consider subscribing to /c/guildwars2@lemmy.wtf as well if you’re able. There’s been some odd bugs getting their posts, hopefully that’s ironed out. These projects are still somewhat early in development, but have a promising future!

Also: consider searching #GuildWars2 to see even more discussion from the wider network. If you have any questions about federated social media, please ask them below :D

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

      Would it matter when you are trying to reach lemmy.wtf from kbin.social? The Cloudflare Challenge shouldn’t do anything for outgoing from Kbin.social.

      I use Cloudflare and Cloudflare Tunnel for lemmy.wtf as well, so maybe Cloudflare is blocking Kbin.social’s request?

      • Necropola❌@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        As far as I understand you are both using Cloudflare and I assume that the Cloudflare Challange only hits incoming connections, but I have no practical experience with Cloudflare myself.

        Anyway, when both lemmy.wtf as well as kbin.social are using Cloudflare, then traffic is always incoming via Cloudflare whenever those instances are trying to communicate/federate with each other.

        I’ve found posts which suggest to exclude certain paths/URLs from bot detection thereby suppressing the Challenge when a bot does what a bot is supposed to do, but there also appears to be an Essentially off setting which one could try temporarily to see whether this solves the issue.

        • Necropola❌@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Looks like kbin.social’s IP is registered on Cloudflare’s DNS servers, but the IP belongs to Fastly.

          Maybe running a lemmy or kbin instance behind Cloudflare isn’t such a good idea after all. Apart from communication problems like federation not working properly there are some serious privacy concerns or rather running federated network traffic through a centralized US based network service kinda contradicts the whole fediverse idea.

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

            I don’t know. Some people over in the kbinmeta group might have an answer for you. I just know that when kbin had cloudflare turned on we couldn’t communicate with anyone outside of kbin.

      • man0fbass@kbin.socialOP
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        iirc that was happening for kbin.social for a while during a ddos attack. cloudflare does mess with federation quite a bit.