in reply to Re: Extra CSS for "new nodes" when viewing a thread
in thread Extra CSS for "new nodes" when viewing a thread

Read before you speak ;-)


holli, /regexed monk/
  • Comment on Re^2: Extra CSS for "new nodes" when viewing a thread

Replies are listed 'Best First'.
Re^3: Extra CSS for "new nodes" when viewing a thread
by BrowserUk (Patriarch) on Aug 22, 2007 at 19:29 UTC
    Read before you speak ;-)

    Sorry Holli, but could you please explain what you mean by this?

    Maybe Gavin understands (or not), but as one of the gallery following along, I do not see any context in this thread that explains what he should have read before speaking?


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

      holli suggested marking replies newer than the last time the user clicked "I've checked all of these". That's radically different from almut's suggestion to mark replies which have been added since the thread was last visited.

      tye only struct down almut's suggestion, not holli's. It's tye's post that needed rereading.

      holli's suggestion is actually quite cheap. All that's needed is to fetch the RAT/NN timestamp associated with the user (which could be fetched at the same time as other user info is fetched) and the timestamp of every post (which is already fetched).

      almut's suggestion would require creating a new timestamp for every thread every user visits and fetching numerous timestamps everytime a thread is displayed.

        i still thing, btw, that doing on clientside could be nice: 15days cookies and js?