Hoping the hackathon is still running, or folks can discuss. Secure is pretty slow lately, day and night.... Sometimes, the revised articles don't show up for the non-logged-in, but that's easy to fix with &action=purge. I just have to remember to check after sessions. But lately, and fairly consistently, as I've checked the history to compare with Google's cache date (not logged-in), I've discovered an old history seems to be served. "&action=history&action=purge" doesn't fix it. Yeah, I've flushed my own local browser cache. That's not it. The only solution I've found is to log-in insecure, check the history, and then log out. Then, the history is up-to-date for non-logged-in. Why do we cache history?

Aha, replication lag would explain it!  Since I'm only doing things on off hours, how long should replication lag be these days?