I've been noticing an issue in the last few days where threads that I've completely read don't 'remember' that I've read all the replies.
I think this is a 'server side' issue as I see exactly the same issue on my PC (Windows 10 & Chrome) and iPhone (Chrome or Safari).
I don't know if the devs are close to figuring out this issue, but based on a tiny bit of observation, I think there's a link between this issue, and the one in this thread: viewtopic.php?f=12&t=1373943
(where I figured that a post's timestamp on the server is different based on what network the user is posting from).
Basically, I've noticed that if the timestamp of the most recent post is "too far into the future" compared to the timestamp of whatever I'm reading from, it won't mark it as read. Basically, my hypothesis is that marking threads as read is based on comparing the timestamp of the last post to the timestamp of the reader's system when the post is read. For example, last post is at 10:04 am, and you read the thread at 10:05 am, so therefore, it gets marked read.
The problem comes in that the a.net server isn't using a single server clock to date/timestamp posts, but rather is somehow depending on the timestamp of the server from which the post is coming (which, somehow, are not all in sync with any standard clocks or what have you). I've noticed that when posting from my home computer network, timestamps tend to be about 3 minutes in the future vs. real time (my computer, which is synced automatically with what should, in theory, be accurate to within a fraction of a second, says the current time is 9:51 am Central Standard Time, but I bet that when I submit this post, the timestamp on the post will say 9:53 or 9:54 am central time).
Other users have different errors in timestamp vs. real time (when I post from my cell phone using the cell network instead of home wifi, the difference is closer to 7 minutes), and so when you read a post that was just posted, by someone whose server is posting farther "into the future" than yours, it won't be marked read right away. I noticed this this morning when I read a thread whose latest post was 5 minutes in the future. It wasn't marked read, despite me reading it several times. Once a couple minutes had passed, and the timestamp was now 3 minutes away (i.e. equal to what my account is doing), the thread was marked read.
Hopefully someone can send this note to the developers if they're not already aware of the issue and what's causing it.
The plural of Airbus is Airbuses. Airbii is not a word.
There is no 787-800, nor 787-900 or 747-800. It's 787-8, 787-9, and 747-8.
A321neoLR is also unnecessary. It's simply A321LR.
Airplanes don't have isles, they have aisles.