UPDATE (4/27): There were two reasons that affected federation between Ani.Social and Lemmy.World.

The first reason was an outgoing activity that got stuck in queue. This was resolved by manually marking that activity as successful.

The second reason was a subsea fiber cut between Europe and Asia which caused incoming activities from Lemmy.World to lag behind.

The original plan was to move Ani.Social closer to Lemmy.World this weekend but seeing the activity queue rapidly dropping over the past two days, it’s unlikely this will push through. We will continue to monitor this however.

Again, thanks to @wjs018 for informing me about this and for keeping others up to date in this post’s comments. Thank you MrKaplan from Lemmy.World for helping us resolve the issue!


There are ongoing issues between incoming and outgoing activities between Ani.Social and Lemmy.World. Posts, comments, and votes from both instances are not in sync with each other.

The exact cause is to be determined. The instance may experience downtime and interruptions until further notice.

In the meantime, we suggest using an account on an instance that is federated with both Ani.Social and Lemmy.World.

Thanks to @wjs018 for informing me about this issue. Thanks also to MrKaplan from the Lemmy.World team for continuously helping us resolve this issue.

  • wjs018
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    7 months ago

    Yeah, it’s a weird situation. I am not removing duplicates that haven’t federated over yet. Until posts federate to ani.social, no other, third-party instances see them. The situation is growing worse too. The current delay is up to ~12 hours behind.

    Edit: Currently improving, back down to ~8.5 hours.