Clearly this IS a bug and not a feature. No doubt. And, yes, this has already been a properly filed (but ignored) "request" for at least a year or more. That's

Clearly this IS a bug and not a feature. No doubt. And, yes, this has already been a properly filed (but ignored) "request" for at least a year or more. That's why I'm always glad to see it pop up as a regular post. If HN is listening, here's the fix: Make the [more] link go to its best guess by TIME or by RANK (depending on which is being shown). Who cares if the sequence numbers match (i.e. 39 was last on the page, you click next and 44 is at the top of the page)? If that bothers anal retentive types then include a NEXTSEQ variable in the [more] link so the page can fake it. Again, who cares if my #44 is your #32? This is a news feed not a database-of-record. Does this "paper over" the problem? Sure, but the user experience would be all the better for it. Just make [more] work please.