cross-posted from: https://lucitt.social/post/6959

Is anybody else running into this problem?

My federated posts are appearing in my timeline quite well, however I’ve noticed that significant portions of the comment section are not being carried over.

For example, I’ll see a post on my instance with 13 comments. I’ll click on the fediverse icon to take me to the original source and that has 43 comments. Where did those 30 comments go?

The worst part is, I can’t seem to figure out a way to “force sync” or refresh the page to make sure all the comments are carried over. Because of this, I feel like I’m only getting part of the conversation and I’m unable to reply to comments that don’t appear on my instance.

Does anybody have any solutions to this problem? It’s literally my one huge issue I have with my own instance.

  • Slashzero@hakbox.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I haven’t seen that issue on my instance, but admittedly I’m not thoroughly checking comment replies. I just checked a few now and comment replies match.

  • RoundSparrow@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Since your instance is new and small, keep in mind that there is no ‘back fill of data’, the replication of comments and messages only starts once the first person on your server subscribes/joins to a community on the remote. It does copy over a handful of postings, but no comments.

    From that point forward, then there are reliability problems that are widespread, see Github issue: https://github.com/LemmyNet/lemmy/issues/3101

  • Jamie@jamie.moe
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    You can force sync a single comment by going to the original instance and getting the /comment/#### link, and searching it in your own instance. It could be possible to automate this via the resolveObject API call, but a lot of people doing it en masse wouldn’t be good for the big indtances.

    It boils down to either your instance not using with workers to handle activityhub updates, or the big places being overloaded and experiencing the same thing. If they don’t get to successfully send you an update, or you fail to receive it in time, you miss out on that content.