Federation is broken.

It's been broken for days - and that's not to say for months, because I charitably include the few hours it worked again lately for some reason.

I don't know if other instances are that thoroughly broken, because the rest of Lemmy seems to be chugging along just fine. It's just us poor SDF user suckers.

And no-one gives a rat's ass.

Truly pathetic...

you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 2 years ago (4 children)

Looks like there’s a fix incoming: https://github.com/LemmyNet/lemmy/issues/4288#issuecomment-1878442186

FYI, on lemm.ee I have been testing 0.19.1 patched with the #4330 changes by @phiresky for the past week and have noticed no further issues with outgoing federation, so I think this issue will be resolved with the next release

That patch has been applied (https://github.com/LemmyNet/lemmy/pull/4330) so now I guess we’re waiting for a release to be cut. Fingers crossed.

  • source
  • hideshow 8 child comments
  • [–] 3 points 2 years ago (1 child)

    Any idea if it'll "catch up" and sync all the messages over the past few days, or just start properly federating new stuff going forward?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (1 child)

    In the past, there's been no catch up. Repost anything you want to be seen.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (2 children)

    Things caught up the last time. I even got replies to some of my comments

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 2 years ago

    Yep. That's a new feature of 0.19.x. It reworked how the federation works, and now it also checks if stuff federated successfully, if not, retry. It was done to make federation more reliable. But of course, new features, new bugs.

    At least that's as far as I know. Don't trust me.

  • source
  • parent
  • [–] 2 points 2 years ago (1 child)

    Whh isn't this affecting other instances?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 years ago

    It is, rebooting a service/system/server or other tinkering by the instance admins has let at least one instance come back. But the bug comes back so it's not a real solution. The instances that don't show the problem might still have it but also have a solution watching to reset when needed.

  • source
  • parent