Not sure what combination of state and events caused this to happen, but I got a chuckle out of it.

    • shagie@programming.dev
      ·
      10 months 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 unchanged... should I be informed that there's a new comment (rather than 0 new comments and so no change)?

      • Ategon@programming.devM
        ·
        10 months ago

        yeah its not the best system but its whats built into lemmy right now. Probably going to look into changing it

        • shagie@programming.dev
          ·
          10 months ago

          Consider the changes that would need to happen if user level instance blocking of comments was available. If a user was to block an instance that was brigading that post, what count should be displayed as the number of posts (and number of new ones)?

    • Die4Ever@programming.dev
      ·
      10 months ago

      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

      • UlrikHD@programming.dev
        ·
        10 months ago

        Yeah, it's probably cheaper than than counting the number of comments since a timestamp though. Pure conjecture on my part though, haven't really done much stuff with SQL.