The trouble is with that is that it is an all-or-nothing approach. You get either 43 106 nodes, or 0. You can't specify to clear all bar the most recent n hundred. When you're coming back after a break, you want to see what threads are active, to see where the discussion is.
I think a sensible addition would be a setting to say "send me no more than N newest nodes", which would translate to a LIMIT clause in the mySQL backend.
print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u' | [reply] |
As I said in my original post. I did go ahead and clear my newest node. I was just pointing out that it was excessivly slow to load. It didn't seem to me that it shoould take so long to load in any case.
EDIT: Chromatic, In response to the follow up... With all due respect, network speed and browser rendering time may contribute, but they are not the entirity of the problem.Go get the newest node page with 100 days of nodes with something like wget where you can watch the transaction as it proceeds and you'll see that it can be a full 2 minutes before a single byte of body data comes back. That is of course in the cases where it comes back at all. Often wget will report a premature end of headers and have to retry.
-monkfish (The Fishy Monk) | [reply] |