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.

  • jcg@halubilo.socialEnglish
    1·
    2 years ago

    Yep, it’s because of the volume of comments/posts going through the big instances right now, and how many people are subscribed outside of those instances. It’s too much for the server to keep up. I noticed over the last day or two my feed has mostly been Beehaw.org stuff because they don’t seem to be having as hard of a time. It sure is looking like we need more separation like startrek.website, and maybe it was a bad idea to allow communities to just be made by anyone on lemmy.world and sh.itjust.works. Would’ve made more sense for all the users to be on these instances, but the communities hosted elsewhere.

    • Eddie@lucitt.socialOPEnglish
      1·
      2 years ago

      Yeah, I definitely agree that open communities was/is a mistake. If a server is that large, it should be admin only. They can always run polls to gauge interest before making new communities.

      Communities are the biggest problem. One solution would be to make community names more like a federation signature that only allows one community to have that exact name. Example: if lemmy.world has a community called !AITA, and you try to make a community on beehaw with the same !AITA name, it would not allow it and say “sorry that community name has already been registered by another instance”.

      Of course, the major issue with this idea is that one could defederate with lemmy.world, in this example, and make the community name anyway, then refederate. Who would keep the name? That’s why I don’t think this solution is ideal, but it’s fun to share ideas and something to think about.