A way of marking all of them as read and than displaying them with 50% opacity or with another border/background would be a great time saver.
What do you think?
Post a Comment
IIRC, there are about 10,000 comments on Osnews, or maybe more. Keeping track of read markers for every user for every comment on the server would be a ridiculous performance hit.
Keeping a list of every comment in cookies on the client wouldn't work either, for performance reasons.
The only way to do this would be to record the highest current comment id, and then mark any comments with a higher ID as unread on the next viewing, but then how often do you update the reference id?
Keeping the highest comment ID as a marker would work really well. And they could make a link like "Mark all comments as read" to update it only if the user uses this feature. Also they could delete markers from stories that are more than 7 days old, because it would be rather unlikely that those stories would get new comments.
Every forum in existence does it.
PhpBB, the only forum whose implementation I am familiar with, simply marks everything that has been posted since the last time a user visited as unread, and then tracks via (I think) a session cookie what gets read. This way there is almost no added load to SQL.
All you'd do is record the last time that thread was visited thus any posts > last visit date = 50% opacity.
It's quite a good idea for those of us who view OSN in nested view.





