As the lemmy.ca community has been growing, I’ve begun to look at some of your /c/communities and … things are bugged. I can’t really post or comment very well on my https://lemmy.world account.

So I created this local https://lemmy.ca account to maybe bring attention to this federation problem.

I’m not sure if this is due to the growth of https://lemmy.world, or some configuration issue on the backend. But I figure that tracking and testing my account access from both sides can help everyone get to the bottom of this.

  • TruckBCMA
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    I have a report that this was resolved as of about an hour and a half ago.

    Please let me know if it’s still an issue.

    • dragontamerOP
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      On this subject: the https://lemmy.world administrators have been investigating the federation issue on their end (see: https://lemmy.world/post/818810). Note that https://lemmy.world is still on version 0.17.4.

      I’m wondering if the problem could be on the https://lemmy.ca end as well, or a bug in 0.18.0. In either case, I felt the need to report this federation-bug.

      I know that various lemmy-administrators have been forced to tweak worker-settings and play around with timeouts to get federation working correctly (or at least, working better). The default settings are simply not workable, not with the #RedditBlackout growth upon this corner of the Fediverse.

      • ShadowMA
        link
        fedilink
        arrow-up
        8
        ·
        1 year ago

        There are known federation issues with 0.18.0 that are supposed to be fixed in 0.18.1. We’ll be upgrading this weekend hopefully.

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

      Hey hey, this one worked!! Trying a reply and going the other way.

  • errorgap
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    It’s not just federation. For at least a good week, those with certain clients would get messages about it being an outdated version. Apparently they’re waiting for a patch to fix captcha’s before moving up so, fair enough. Content actually continued to load.

    However, today opening jerboa crashed it when attempting to contact lemmy.world. Only clearing out disk/cache helped with this, but this of course resulted in all accounts being logged out, and the lemmy.world one being unable to login again (possibly due to the version mismatch, possibly due to other issues).

    I’m hoping what things get patched up it’ll be good again but for now Lemmy in general is more of a beta, and I fear it’ll get worse as Reddit drops the hammer on the API and kills 3rd-party clients

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

        Woah, even the old post finally went through. That one took more days of waiting, but whatever the admins did this past weekend must have allowed it to go through finally.

        • Anony Moose
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Yeah, I’m guessing there was a huge backlogs of posts and comments that were in the federation queue or something.