Quote:
Originally Posted by
tylrwnzl 
I think it's a good idea but my only concern is how its implemented. If they use Java to create a live updating scroll it will make Epic even slower for users running IE8 and below because their Java rendering engines are slow. Perhaps if it's not done real time and just on a page refresh it won't be too bad.
Good point. Epic can be pretty slow, so nothing to add to that. The Twitter model not so good then from the loading standpoint.
Still, it is pretty standard web user interface these days to have "last in, first displayed", and present a chunk of content with a "show more" button at the bottom of the page. Start with last X number of posts, click "show more" to see X more in same page. (X could be 30, or some other number.)
Quote:
Originally Posted by
GarryZ 
Why not just an option of last post first or last ? Descending order or ascending.
If sticking with the discrete page model that would be a nice option. And the page model does mitigate potential resource issues for posts that are loaded with large numbers of pics. That could be a problem with a "show more" model viewing something like "More Retro Memories...".