Does anybody know how to go far back within those tumblr "archives" that ain't e.g. 12 new photos on each new page, and where by this you can select page 124, by its number, within the address line, but which are made of just ONE, endlessly scrolling page? Let's say you want to see what they did publish there some 3 months ago... prob here, you'd have to scroll down, again and again, the same 1,000 or 1,500 photos, before even reaching the first photo you might be interested in! I won't give you response times for this in IE8, they are incredibly awful even for the first 500 such photos... but Chrome isn't THAT much better here on my system (with 2 GB of memory), so how to do it, or what to do alternatively, except for making a spider attack in the night?
I even thought of "hiding photos" when endlessly scrolling down, and then "unhide photos" after having scrolled down by a 1,000 photos. Any better idea than that (since it THEN will break my system, trying to display all these 1,000 "unnecessary" pictures, before displaying any "new" (i.e. sufficiently old) one), anyone?
So this is quite an awful web page format, but quite common on tumblr, and perhaps some web specialist here knows how to handle it best, from the outside?
EDIT
I'm sorry, I should have put a question mark at the end of the title line.
Another example of these special "back-loading" pages - or what's the correct denomination of these, in order to google for an answer? - ist this one:
https://chrome.google.com/webstore/category/themes?hl=en
Here again, every "pgdn" or "end" pressing will load more pictures, again and again. Are there elements in the source code that could be of interest, to check, or even to manipulate, in order to get to the "depths" of such a page, more quickly than by incessant, endless scrolling down?
I even thought of "hiding photos" when endlessly scrolling down, and then "unhide photos" after having scrolled down by a 1,000 photos. Any better idea than that (since it THEN will break my system, trying to display all these 1,000 "unnecessary" pictures, before displaying any "new" (i.e. sufficiently old) one), anyone?
So this is quite an awful web page format, but quite common on tumblr, and perhaps some web specialist here knows how to handle it best, from the outside?
EDIT
I'm sorry, I should have put a question mark at the end of the title line.
Another example of these special "back-loading" pages - or what's the correct denomination of these, in order to google for an answer? - ist this one:
https://chrome.google.com/webstore/category/themes?hl=en
Here again, every "pgdn" or "end" pressing will load more pictures, again and again. Are there elements in the source code that could be of interest, to check, or even to manipulate, in order to get to the "depths" of such a page, more quickly than by incessant, endless scrolling down?



