new since last visiting the thread
Note that that wasn't what was proposed. It is also not likely to ever be implemented. Tracking "time of last visit" for every thread for every user is too much overhead. The proposed feature would trigger only based on the "I've checked all of these" buttons found in Newest Nodes and Recently Active Threads.
| [reply] |
Although.... we could cheat.
My typical usage of the site is to find the new posts on Recently Active Threads and then click through to them (or their parents).
We could do the same as Holli suggested for RAT/NN and, if the user has a "time of last visit" set, add a class to the posts on that page that are newer.
It clearly wouldn't work for older threads found on (eg) Seekers of Perl Wisdom, but it wouldn't hurt either. For common usage, it would be fine. And cheap.
Clint
| [reply] |
Ah... thanks for clearing this up, tye. Obviously, my reading of
holli's suggestion was strongly influenced by what I would
like to see implemented... :) Sorry for the confusion.
Anyhow, any improvement along these lines would be greatly welcome,
as what I currently typically do to handle such high-traffic threads is
to click on the (assumably new) "Re^N:"-subthreads in Recently Active Threads, and then -
because I need some more context - click on the parent node link once or
twice. Presuming I'm not the only one doing it this way, this is not only cumbersome to handle, but also
creates a lot of unnecessary requests to the server. —
But of course, I respect the decisions of whoever would have the
trouble implementing the changes.
| [reply] |
Tracking time of last visit on the server side would be hefty, but as I say below if there were a thread last updated item hidden in the HTML javascript could be used to handle this in a cookie on the browser side. Even if just using greasemonkey.
- Ant
- Some of my
best work - (1 2 3)
| [reply] |