I do the majority of my Lemmy use on my own personal instance, and I’ve noticed that some threads are missing comments, some large threads, even large quantities of them. Now, I’m not talking about comments not being present when you first subscribe/discover a community to your instance, in this case, I noticed it with a lemmy.world thread that popped up less than a day ago, very well after I subscribed.
At the time of writing, that thread has 361 comments. When I view the same thread on my instance, I can see 118, that’s a large swathe of missing content for just one thread. I can use the search feature to forcibly resolve a particular comment to my instance and reply to it, but that defeats a lot of the purpose behind having my own instance.
So has anyone else noticed something similar happening? I know my instance hasn’t gone down since I created it, so it couldn’t be that.
I’ve noticed some similar issues on my instance, but I’m wondering if it’s related to how much strain is currently on the bigger instances like lemmy.world or beehaw.
From what I read in the troubleshooting guide, if their worker count isn’t high enough, the issue can start on their end, too.
Maybe one day the servers will implement a call to backtrack for missing content. Because I could see federation failures like this being a big missing point for wide adoption.
It’s possible to do via the API as is if you were to connect to the first instance, then call resolveobject enough times on your home instance if there’s a discrepancy. But that would require an individual API call for every missing object, and it would be painful for big instances.