It seems like just recently, everything broke. Posts from some other instances (Lemmy 0.19 or kbin) aren't showing up here reliably anymore, and then sometimes posts from a few days ago will suddenly show up. kbin.social has a banner talking about unusual "problems" without going into detail.

Does anyone know what's going on or why? I've heard that Lemmy 0.19 has a problem where its outbound federation queue will sometimes die until it's restarted manually, but that doesn't seem like it should affect a lemmy.world <-> kbin interaction. Is it just Lemmy 0.19, or just lemmy.world, or are there multiple issues, or what gives?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago (1 children)

Granted my instance is tiny, but have had zero noticeable issues with 0.19.1 since updating weeks ago. It had some increase in CPU on deployment due to DB and Pictrs also doing DB upgrades (or upgrade prep - depending if you stayed on 4.7 or went to 5), but has been running fine since.

[–] [email protected] 7 points 1 year ago (2 children)

Mines also tiny and my timeline is all fucked up since updating.

Posts I just make are 11 hours old the second I send them and I’m getting about 60% of the content I see when I browse the original instance of a community coming through on my side.

[–] [email protected] 4 points 1 year ago (1 children)

Check this

https://phiresky.github.io/lemmy-federation-state/site?domain=quokk.au

AFAIK, in order to fix outgoing federation issue, you need to restart Lemmy and DB every few hours. This is a temporary solution

[–] [email protected] 3 points 1 year ago

Cheers for that!

1337 lagging instances

Woo!

[–] [email protected] 1 points 1 year ago

Weird, did you run any of the alpha/beta/rc builds? I did and maybe that somehow made my upgrade smoother?