|It has always worked like that. It does not record, per user, which posts you have read. To do that, it would need to record, for all 55,603 threads (at present), for each of 4,905 users (at present) whether or not each one has read a particular thread. That is, 55603 * 4905 = 272,732,715 database records to do that.|
What it does is record, on your user database entry the *latest* post you read, and update the list of posts accordingly (shown as read or unread).
However there is one exception, which you noted. It doesn't count, if you read your own post. Why? Well, if you have (say) 5 unread posts. You read the first unread one, so it looks like this:
The "read" marker now is between d and e, because you read e.
However if you now reply to e, with post r1, it looks like this:
r1 (your reply)
However note that r1 is not marked as read, because if it was, it would also look like a, b, c and d were also read (which they weren't).
So, if you replied to all 5 posts (which I often do), I then see:
So, effectively my own posts are marked as unread, although obviously I don't need to read something I wrote myself, so I don't worry about it too much. Later on, another post from someone else, which I read, effectively moves the marker up, so all posts are now read.
- Nick Gammon
| top |