Poppidirk and Merl probably aren't the only ones to have questions, just the only ones brave enough to ask. I'm very close to a DAU myself, certainly not a techie, but I'll give it a shot. Maybe it would help to say that a cache is a place to store copies of files (like a pirate has a treasure cache, or a squirrel caches away nuts).
Google makes a copy of each file when its robots crawl the net, and keeps the copies on its server until the next time a robot visits the same address. (I don't know how often that is, but apparently not more often than a couple of weeks, since it still has all the old LEO links.)
Your browser makes a copy of every web page you visit, so that if you go back to the same page, it can load the file fast from your hard drive instead of slower from your internet connection. For web pages that aren't frequently updated, that saves you time.
However, when the file is one like LEO pages that changes constantly, either the LEO software has to prompt your browser to refresh (reload) the file again from the internet, or you have to press F5 (or Reload/Refresh) yourself. Otherwise you may get an non-updated version of a page.
A problem I recently encountered, though, was that even after I had reloaded the page once
(and seen my new post on it), I later was sent back to an older version of the same page (without my post) when I clicked on the link coming from a different direction, namely, from Startseite instead of from Antwort Senden. I mentioned it in an earlier thread called Auto-F5 and duplicate posts
, but I'm not sure if anyone noticed it or understood my point.
So I suspect that the failure to update all versions of the same URL might have something to do with an unusual number of duplicate posts, because if you didn't know that the software wasn't updating correctly, you might really try conscientiously to F5 and think you had proved that the post hadn't gone through, when in fact it had.
In a case like that, where the cache contained two versions, one new and one old, you wouldn't have any idea that that was the problem, so that you actually needed to not only update the page, but actually delete files from your cache (i.e., empty the LEO files out of your folder called Temporary Internet Files), or force your browser to overwrite them (CTRL-F5, apparently; thanks for that tip, Jalapeño).
In fact, probably a lot of people don't even know that CTRL-F5 exists; at least, I certainly didn't. Does it mean only delete the cached version of that one file, or does that command mean 'Empty the entire folder of all cached files'?
I'm also still not sure I understand whether that would solve the problem if the error is really that there are really two versions of the same file, i.e., two URLs for the same discussion (one generated by approaching from one page, like the reply page, another generated by approaching from another, like the overview).
Or in fact, whether there's really any difference between F5 and CTRL-F5 on a site like LEO where the script loads the page from the server again each time anyway.
So if all those questions (obviously not urgent) put me back in the DAU group, sorry, but at least maybe I'll be in good company. (-: