If you need to edit your comment, make sure you fill out the "reason" field or the change may not stick. You can put anything into this box--even just a single letter--and it seems to do the trick.
Simplified, a functioning website has to access a lot of internal resources to produce a web page - things like user and post \ comment database, store some logs and metrics, etc. A very heavy task just for producing a single piece of HTML text (not even counting embedded elements, like fonts and images).
Cacheing is a technique that allows web pages that are frequently accessed to be stored already prepared in soome kind of easily available location (dedicated caching web server memory). Once you request resource from webserver, first the cache is checked if that resource exists there. If it does, you are served object from cache.
If resource is supposed to be changing with time (like new comments added for a post), cache has some explicit timeout when resource cache copy is considered to be stale and it is automatically expunged from cache.
The more website is loaded, the more "aggressive" caching becomes (higher cache timeouts). usually though it does not exceed some sane value, like 1-2 min max.
Comments take time to load.
Related pro-tip:
If you need to edit your comment, make sure you fill out the "reason" field or the change may not stick. You can put anything into this box--even just a single letter--and it seems to do the trick.
There’s a delay between submission and view
It's caching.
Simplified, a functioning website has to access a lot of internal resources to produce a web page - things like user and post \ comment database, store some logs and metrics, etc. A very heavy task just for producing a single piece of HTML text (not even counting embedded elements, like fonts and images).
Cacheing is a technique that allows web pages that are frequently accessed to be stored already prepared in soome kind of easily available location (dedicated caching web server memory). Once you request resource from webserver, first the cache is checked if that resource exists there. If it does, you are served object from cache.
If resource is supposed to be changing with time (like new comments added for a post), cache has some explicit timeout when resource cache copy is considered to be stale and it is automatically expunged from cache.
The more website is loaded, the more "aggressive" caching becomes (higher cache timeouts). usually though it does not exceed some sane value, like 1-2 min max.
The site takes a while t update and it updates asynchronously. So you may have some items update sooner than others.
Nah.
testing comments section ... are you receiving us?