When we come back to a previous read thread there’s a thread with text in brackets showing the number of new comments made since we last visted that thread. These new comments are not differentiated from the old comments in any way. So unless we have a very good memory we won’t be able to figure out what is new or old.

Hence this feature request - please hilight the new comments somehow. Maybe a lighter/darker/different colour background than the rest of the posts.

  • Gormadt
    link
    7
    edit-2
    11 months ago

    I’m not sure either but one thing Jerboa does seem to do is tell you how many new comments have arrived since the last time you were on the post.

    Maybe based off of the existing code kinda like

    Check time of last visit

    Check for new comments since last visit

    Show number of new comments

    Check time stamps of comments when thread is opened vs time since last visit

    Highlight those comments

    I haven’t coded in a long time so I’d probably be as helpful as a toddler holding the flashlight while someone works on the car if I tried to do it.

    • MV [Jerboa dev]
      link
      fedilink
      411 months ago

      Jerboa knows that information because it is part of the api. The above feature request is not

      Checking time is a good idea but then Jerboa has to store per post per instance per account each timestamp. It also gets pretty complicated when new comments are part of a thread. It would ve to fully load the entire comment tree. I rather see this supported in the API with a new sort option unread

      • Same, but it is feasible outside the API as well by creating a lookup table. You could use the same to track whether the comment is collapsed, viewed comments, etc. Just make a table with:

        • comment ID
        • whatever flags you’re interested in
        • row creation time
        • data from the post - modified time, for example

        Then as you’re creating posts, reference that db and make the appropriate changes. Have an option to clear old settings after some time based on the row creation time (say, a week) so storage doesn’t grow indefinitely

        It’s feasible, but there’s a fair amount of work there.