I doubt it is a federation issue. The number of comments will be worked out by the number of comments in the local DB. So the count won’t include comments not received.
As to why they’re not showing, as mentioned above, hiding bot comments, or perhaps deleted comments still appear in totals (not sure about lemmy, on kbin deleted comments have their text changed to indicate they were deleted).
Being the only person on my instance subscribed to certain communities on other instances, I am pretty sure it is a federation issue. When I look at the comment counts for the same post on two different instance accounts, they are not the same. They often share the same comments, but not all of them. Sometimes the number shown below the post reflects only the comments from the instance you’re viewing it on, sometimes it shows all of them.
For example, looking at the Baldur’s Gate 3 community on Lemmy World when logged on to Lemmy World, the top post has about 36 comments but counting them in the post there are only 30. 3 of those comments are mine, and they aren’t being shown to my Lemmy World account. When I view it from Yiffit, only my 3 comments appear, while it also says there are 36 total.
Different comment counts between instances is a federation thing, yes. But showing a number of comments different to the comments shown on the same instance, not.
There are reasons for missing comments, especially on communities from lemmy.world right now. But that’s not what is being reported. A federation message for a post does not contain the number of comments (and that would be a totally pointless property to send). It’s also quite common that certain comments don’t make it over federation.
The screenshot is showing a comment count without comments, that means the instance has one comment locally but for some reason is now showing it. That’s not a federation thing.
This is a known kbin/lemmy thing. Kbin sends dates with a timezone attached, lemmy expects UTC. I actually keep meaning to set the server to UTC to stop this happening.
I doubt it is a federation issue. The number of comments will be worked out by the number of comments in the local DB. So the count won’t include comments not received.
As to why they’re not showing, as mentioned above, hiding bot comments, or perhaps deleted comments still appear in totals (not sure about lemmy, on kbin deleted comments have their text changed to indicate they were deleted).
Being the only person on my instance subscribed to certain communities on other instances, I am pretty sure it is a federation issue. When I look at the comment counts for the same post on two different instance accounts, they are not the same. They often share the same comments, but not all of them. Sometimes the number shown below the post reflects only the comments from the instance you’re viewing it on, sometimes it shows all of them.
For example, looking at the Baldur’s Gate 3 community on Lemmy World when logged on to Lemmy World, the top post has about 36 comments but counting them in the post there are only 30. 3 of those comments are mine, and they aren’t being shown to my Lemmy World account. When I view it from Yiffit, only my 3 comments appear, while it also says there are 36 total.
Different comment counts between instances is a federation thing, yes. But showing a number of comments different to the comments shown on the same instance, not.
There are reasons for missing comments, especially on communities from lemmy.world right now. But that’s not what is being reported. A federation message for a post does not contain the number of comments (and that would be a totally pointless property to send). It’s also quite common that certain comments don’t make it over federation.
The screenshot is showing a comment count without comments, that means the instance has one comment locally but for some reason is now showing it. That’s not a federation thing.
Says the comment posted 107 minutes in the future, apparently
This is a known kbin/lemmy thing. Kbin sends dates with a timezone attached, lemmy expects UTC. I actually keep meaning to set the server to UTC to stop this happening.
Iirc the Lemmy devs are aware of this and working on it.
Yeah, we can also solve it by setting server to UTC. Hopefully the time on this comment is better.
EDIT: Apparently not. How odd, I changed the server timezone.