• sven@l.mchome.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    You are doing nothing wrong. Due to the load, kbin.social enabled Cloudflare protection which breaks their federating with other servers. Until they turn that off, they won’t properly propagate to other servers.

    • fatcat@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Same issue here. I found this thread via the search function. Did it start working for you at some point? @sunbeam60@lemmy.one @kionite231@lemmy.ca

      • sunbeam60OP
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Nope, seems it’s a cloudflare issue in front of kbin.social

        • fatcat@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I think he disabled cloudflare already. But maybe federation is still not working properly. Thanks for the info, good to hear I’m not alone with this issue. But I think they will have this up and running soon. Nobody expected the huge amount of users, it will take a while to adjust.

  • Lockely@pawb.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    From what I’ve noticed, if its the first time someone has searched for it, it may not appear initially. You basically just prompted the servers to talk to each other. Give it five mins then search for the name of the community directly, i.e. Tech, and it should show up as Tech @kbin.social

  • Evkob@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    kbin.social currently has Cloudfare DDOS protection enabled (presumably to deal with the explosion in user numbers) which messes with federation.

    I believe I’ve seen people on here say that this is just a temporary measure, though. I hope so, there are a few communities over there I’d love to participate in.

  • Kamirose@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Instead of searching for the !tech@kbin.social, try pasting the url itself into the searchbar.

    Kbin is newer software than lemmy and is also being hit pretty hard by the reddit exodus right now so it also just might not be working.

  • LovelyCupcake@feddit.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    What’s the difference between kbin and lemmy? Tried to look it up, but it seems most treat them as interchangable

    • sunbeam60OP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I guess that’s the wonder of ActivityPub?

  • shortwavesurfer@monero.house
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I think the “!” Syntax is lemmy specific. Try the “@” symbol in its place. For example if i wanted to follow asklemmy from mastodon i would have to enter @asklemmy@lemmy.ml to get it. Otherwise use the full https link such as https://kbin.social/m/tech

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

    Kbin isn’t playing nicely with federating at the moment. What I’ve been reading is that the cloud flair ddos protection is disrupting the automated requests from the instance.

  • Generator@lemmy.pt
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    It’s possible, just not at the due to anti-ddos protection.

    But it works with other Kbin instances, like https://karab.in/m/tech
    Just need to wait for kbin.social becomes stable and its possible to federate magazines

  • darius@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    AFAIK because of the cloudflare check federation is now broken between kbin.social and the rest of the fediverse. Please somebody correct me if I’m wrong.