Not sure what combination of state and events caused this to happen, but I got a chuckle out of it.
comment_count - old_count
after a moderator deleted some comments would be my bet.
Submitted 1 year ago by shagie@programming.dev to meta@programming.dev
https://programming.dev/pictrs/image/81a12873-5982-448b-aa60-84a12259001a.png
Not sure what combination of state and events caused this to happen, but I got a chuckle out of it.
comment_count - old_count
after a moderator deleted some comments would be my bet.
more importantly that means if a comment is deleted and there’s also 1 new comment, then it’ll tell you there’s 0 new comments
Yeah, it’s probably cheaper than than counting the number of comments since a timestamp though. Pure conjecture though on my part though, haven’t really done much stuff with SQL.
Ategon@programming.dev 1 year ago
-1 New means that one of the comments got deleted since you last checked the post
shagie@programming.dev 1 year ago
If the post had 93 comments last time and has 92 now… is that noteworthy?
And if there was one new comment and one deleted comment leaving the resulting sum total of comments remain unchanged… should I be informed that there’s a new comment (rather than 0 new comments and so no change)?
Ategon@programming.dev 1 year ago
yeah its not the best system but its whats built into lemmy right now.Probably oging to look into changing it