• SuitedUpDev
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I just tried it on my instance, not getting any results however, I believe it probably has something to do with the server capacity (on either ends).

      • SuitedUpDev
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Probably growing pains. The federation is obviously happening between those servers but the exchange of data only happens if you actually if a user subscribes. But probably Kbin has some servers issues.

        I’ve been seeing server errors at Kbin, every time I tried to look it at.

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

          Yep they’re on fire, husband was on there but has temporarily moved back to Lemmy since Kbin isn’t federating. They’ll sort it aaaaht I’m sure.

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

            Yeah, it’s just a matter of time. I saw the same thing happen during the initial wave of the Twitter migration.

            All instances were smoking… Notifications took 10 minutes to arrive, messages sometimes even hours 😂