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

  • 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.