The way we “force federation” is to tell reddthat to “resolve” the comment/post via the API. It’s a roundabout way to force all of the content to still appear.
It’s interesting that it doesn’t trigger notifications but I’m not surprised it doesn’t and when you think about it makes some sort of sense.
The 5-7 day delay is when the actual comment/post is federated from LW as the “time behind” value is 6.3 days currently (and coming down).
I’m reaching out to one of the other admins who apparently wrote their own federation queue. That means we could return a 200 OK response instantly for everything and work on the queue on our own time.
There is still not that much movement on the dev side as it’s a complex problem and the devs don’t seem to want to develop something like a queue currently. Which I understand as it would be a completely new system and would need lots of testing…
On-top of that, every “jump” in backlog results from some abusive kbin bugs. Kbin has some users who send a like and an unlike constantly. In the order of 50k requests in an hour. They like and unlike a post on LW. LW then has to federate ever like and unlike activity. Which ends up being 50k Activites that need to be sent per-server. So it makes federation lag for everyone.
So we’ve managed to catch-up a bit each day and then some kbin bug causes an issue and then we are now +1 extra day behind.
Hearing about the lack of notifications is disheartening. Is it so hard for a system to have some sort of quorum? :(
Hopefully we get something sorted in the next week or two… Otherwise I might block every vote coming in until we catch-up. (As votes account for over 90% of activities).