There is the same problem on reddit, so they brought it here too so new users won’t be disoriented (/s)
Didn’t that have something to do with shadow bans on Reddit?
Or comments pending of mod approval.
I mod a few communities and haven’t seen anything relating to comments pending mod approval. The only related setting I have on the communities is to restrict posting to moderators (comments on the posts should still be open to anyone).
It’s pretty easy to see on r/askeconomics. All top-level comments there require mod approval, but will add to the number of comments while waiting for approval. So it’s pretty common to see posts with 10+ comments listed, but nothing besides the pinned automod comment is visible.
Oh you meant on Reddit. I was talking about here on Lemmy we don’t have anything like that.
Are you and OP on the same instance? If not, the phantom comment could be from an instance federated with theirs but not yours.
I accidentally made a post that has -3 comments.
This happens because Lemmy does not count the actual number of comments that there are under the post, but instead there is a counter per post. This is not necessarily a bad thing, but it does not seem like the counter is every synced with the actual count of comments.
I think I noticed that if a commenter deleted their comment then the total comments would go down by 1. On a post with only one comment that also got deleted, it made it show as -1 comments.
deleted by creator
Ok, so basically, there is multiple ways one could comment count. The most obvious option is to count the actual number of comments under the post. This might be in practice slow, as you must load all comments under the post. An alternative approach is to have a count variable for post, which is increased or decreased by 1 if post is added/removed. It’s way faster to retrieve that variable, instead of getting all comments and counting the number of them. The problem starts if some anomaly happens that is not accounted for, so for example, if I request the same comment to be deleted multiple times. So that counter can be decreased more than once for the same comment. This could be fixed pretty easily:
if comment_to_delete is deleted { // Do not do anything return } post.comment_count -= 1 delete_comment(comment_to_delete)And yeah, I thought so too, but ever since I stumbled upon this bug, I think the way the comment count is stored is through the counter variable.
deleted by creator
because when you load any page listing posts, you don’t want your server to have to go and download the actual entire comment thread for every post that is listed. And then have to go and count how many there are.
Because it would be slow, especially with multiple servers involved. Every time you loaded your home page or a community the server would have to start from scratch gathering the data. It would be more accurate but it would be very hard. And not give a lot of extra value.
So it’s more efficient to have a piece of data attached to the post that just reports the number of comments. Same way as there is a piece of data that contains the title, the name of the person who posted it etc. And that value is updated in some way. Apparently in a way that has not yet been perfected. :)
deleted by creator
Getting the total number of all comments may be very resource heavy if there is a lot of comments.
If it’s just 5 comments, then the computer can quickly get them all from database and count how many of them are there. Now imagine if there is 50 000 comments and suddenly, you me and entire website ask “how many comments are there for this post?”
Suddenly the computer is overwhelmed by the request and you may end up crashing it due to amount of tasks it has to do.
It’s way faster if instead of all of that, the computer kept track of a number of all comments and simply adjust it when comment is added or removed. It does not have to get all the comments and count how many are there, just simply return the number and you are done.
But in the essence, you sacriface potential accuracy for speed. You may accidentally “desynchronize” the counter - if an user requests a removal of the same comment twice, and you don’t check if that comment was not removed. Or, in theory, if two separate users add or remove a comment at the same time. This is called “race condition”, which is common in multi-threaded computing.
deleted by creator
First method does not store the number itself anywhere. Let’s assume that you store apples. I come and ask you “How many apples do you have?”. To answer, you go and count every single apple one by one and return me the number. It’s very easy if you have a small number of apples, but if you have, let’s say, 5000 apples - you can see how long it may take.
Second option is you keeping a track of how many apples you have in stock by having it written down somewhere. If I ask you “How many apples do you have?” you just pull out your notepad and tell me the number. If you give me an apple, you just adjust the number you have written down already.
I had also read that editing a comment increases the comment count on a post.
Have you disabled viewing posts from bot accounts? It’s one of the user settings.
If you have disabled viewing posts from bots, this is what you would see if a bot commented.
Because data synchronisation between instances is quite poor.
This could be due to federation. Maybe they.are federating with servers that you aren’t.
But Reddit also had a lot of this and people always blamed shadowbans.
comments removed by mods would always show up in the count.
idk why they didn’t just fix that, it made people crazy for no reason.
It’s a distributed system, by its very nature no single universal “truth” exists. That is to say, you can very much see differing counts of ~anything. Or different threads. Or anything, really. There is no way to keep everything consistent, ever.
Do you have a client that shows top comments with a time frame like “last 6 hours”? Maybe the comment is older than that.
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).
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.
I have seen this happen entirely contained on a single instance (community and my account on the same instance) I don’t have bots blocked.
So I suspect something is funky somewhere, will try to see how it displays in other apps(and kbin etc later)
Is it sync? If any case, this kind of questions are usually better in the app community
Removed by mod
Are you sure you replied to the right comment? I’d rather see comments like theirs than responses like yours. I can’t find anything in their words that merits your toxicity. If one of you sounds miserable, it’s not
Izzent.Blaze.Nice username, by the way!
Unfortunately the person who replied must have missed it.
Thanks! 🙂
Removed by mod
Just thought maybe you actually had replied to the wrong comment because yours was so ridiculously over the top, rude, and toxic.
I now see that’s just how you communicate.
Grow the fuck up and let discussions happen. Maybe you’re miserable, but keep it to yourself.
Moving along now…
Actually, reading the question again, I kind of agree with you on the fact that this discussion should happen here.
The way you phrased, however, is way too aggressive.
Judging by how you seem to take everything as some sort of personal attack, the amount of disturbances you must go through every day, sounds exhausting. You are not that energy.
Damn, do you really to be that aggressive?
I think they were just suggesting that it should be discussed in the app specific community as they thought it was an app issue not a federation issue.
Hey, it’s you again, hello!
I was going to comment that I keep seeing you around. 👋
