After composing my most recent reply to this thread, I pressed Submit and the browser throbber started spinning as usual. And kept spinning. After a very long wait, I opened the GD thread list in a separate tab (which came up immediately) and checked to see if the thread had been bumped to the top of the page, with my name on the right. It hadn’t, so I hit stop and pressed Submit again. This time it came right up with a message informing me that I had posted a duplicate and took me back to the thread, where, indeed, my post was showing up with all the others. But the GD thread listing never changed. Right now it says there are 76 replies to the thread, but it should say 77, since the last post is numbered 78.
The system does not always update the listing contemperaneously, but rather handles this task in batches, so a bunch will show up and then some more will show up.; it catches up sooner or later, just not right away.
This is especially true when the system has a lot of demand on it, which we seem to be having of late; then the lag time is even greater.
Under extreme stress, the system drops posts it can’t handle altogether, so you were lucky, believe it or not.
The fact that it came up immediately may mean that you got a cached copy (from your browser’s own cache, or one maintained by your ISP, I can’t say). This copy would have been made before you made your post (probably at the time you first viewed the forum listing), and would therefore not include your bump.
A tip, by the way: If you’re not sure if a post went through, hit “preview”. If it went through, you’ll see it there, and if it didn’t, you’ll have another chance to submit it.
Great. “Lucky” enough to be the one ignored, passed over, spurned.
My life in a nutshell.
Chronos, I made sure to hit refresh, though I don’t think I should have needed to. If the page has updated, the browser knows not to use the cached version, right?
Anyway, it seems my post has finally been counted, as the reply count now matches the post numbers.