Nothing you can do about it on your end. ActivityPub seems to require the larger instances to send outbound notifications, messages received more than 10 seconds old are tossed out, and it appears right now the larger instances can’t keep up with delivery in that time frame. Makes sense… lemmy.world instance has 3.6K users and 2200+ federated servers. If only 10% of the users upvote one post, that’s over 700K out going notifications already. I’d imagine a larger portion of the current users being more active considering large chunk of us are the more active Redditors seeking refuge…
Lemmy Support
Support / questions about Lemmy.
Active and Hot are kinda weird right now, they're fixed in the next version, but your best way of seeing trending stuff currently is by doing Top Day/Top Week.
Some of the bigger communicaties like Lemmy.world and lemmy.ml are experiencing terrible growing pains from the massive expansion of Lemmy. You can help your own instance by adding more federation workers in the admin panel, assuming your hardware is up to the task, but I think a lot of the missing comments are a factor of the big communities being overloaded.
Increasing my federation workers to 1500 resolved a lot of my warnings in my logs, but I'm still missing tons of comments from Lemmy.world.
I'll try that, thank you for the suggestion. You've also helped me confirm that my instance is federating correctly with lemmy.ml, kbin.social and your own instance as well, so I think we're off to a good start.