Appears to have been quite smooth - please let me know of any issues. We’ll be monitoring performance for the next hour.

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

    That was smooth, I didn’t even notice

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

    Thanks for the work. Can you please check if federation is working correctly with kbin.social? [email protected] and [email protected] seems to be getting some traffic but the number of comments for threads are way less than if I check on kbin.social directly. Another kbin.social community, [email protected] don’t seem to be up to date at all.

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

      This appears the same issue as lemmy was having with other lemmy instances, where activities may not be synced for various reasons. If an activity isn’t properly synced then there isn’t a way to force a re-sync of the data.

      I’ll keep an eye on github and check if anyone else is having these issues and if there is any config changes I can make to help.

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

          Thanks, that does seem to point to where the issue lies, as I get the same response. When this happened on Lemmy it was because the target server was overloaded but I doubt that’s the case for kbin.social, and more likely to be with the communication between servers.

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

              Thanks for making me aware - sounds like a case of bad timing if it appeared to them we were down. Appreciate you making that post and making us aware.