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

[Gavin]

tye has intimated that the overheads would be too great to implement this server side, could it not then be implemented client side through a script?

[suaveant]

Actually... if on pages like newest nodes the html held the last updated thread time then it would be easy to either have javascript on the PM or use GreaseMonkey to store the last time you visited a node... then highlight those that have been updated since you last visit. Should be almost no extra work on the server side. Would be a nice option.

[Popcorn Dave]

That's what I was thinking. Every time you visit a node, couldn't you store the nodes below it locally and if you revisit a node base your CSS on your own data of read nodes? Seems like something that could be hacked together using GreaseMonkey or a Firefox extention.

[holli]

Read before you speak ;-)

[BrowserUk]

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?

[ikegami]

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.