How about I add a {mirror} link that goes to the mirrored root node? I'll work on that tonight.
By waiting for newest nodes, I mean reloading the newest nodes page and then getting a cup of coffee. During peak hours the wait can be 1-2 minutes! So I decided to sacrifice up-to-the-minute nodes for 1-2 second loading of the scroll.
On the technical side, my ISP's policy restricts cron jobs to once an hour at most. And part of the idea is to examine ways to reduce load on PM, so building the scroll on-the-fly is out of the question.
I also find that the links to parent and root nodes save me a TON of time.
--
Bring them on! I prefer a straight fight to all this sneaking around.
|