Rlly strange message listing behaviour?

Ok, so me and @sjr04 replies to this post: and at the time of sending the message i’m confident my post was first, however they were literally sent at the same second.

Checking back on the post, I now discover mine is second:


Now I don’t really care about the actual effects of the issue, but I am curious as to why it happened.

Is this some new behaviour in the ordering of the posts or is this just discourse bugging out given how closely together these messages were sent?

2 Likes

Thank you for this post because this also confuses me when I try to be first in #updates:announcements lol (my reply looks like it’s first but like 5 people already beat me)

I guess that some people are just really fast and really early. Guess I just got lucky

3 Likes

I’ve seen this for a while now, so it can’t be new. Did you edit your post shortly after? Because, IK I did and that’s when my post got moved after the first one. I think this may be a bug, but if it wasn’t I’d think that they’d incorporate this so that it actually allows people who post with a thorough body to be first rather than having people post something immediately and then edit it to write everything in.

And yeah, this is quite heart-shattering when you think that you’re the first to post on Announcement threads, but then it gets moved down… :frowning_face:

1 Like

I haven’t modified the message since sending it, interesting that you say its happened before because I thought it could just be a once in a hundred years things where two posts were literally sent at the exact same time, but maybe there is something more fundimently flawed / this being intended behaviour :thinking:

1 Like

My guess is that the you locally see yours first as you have a local timestamp but then once the server updates to have the post it probably then streams the new “correct” timestamp whenever the server finished processing it. That would be my guess although I could be wrong.

1 Like

It’s likely due to latency. You post, it displays your message locally, and then it starts to send a message to the server to post it for everyone else. Then, before the server handles your post, incapaz posts his message. He posted first, but it didn’t render as first for you because his message was still being processed. This isn’t a forum issue, either, you can see it on other platforms like Discord too.

3 Likes

Honestly. This has happened to me before and it makes me very sad.

“Oh my god! I actually posted first!”

Refreshes

“Wait, what? NOOOOOOooooo

It’s too bad I don’t have great wifi. ╥﹏╥

1 Like

This behaviour needs to be better-defined so maybe a request at meta.discourse.org?