I read my reading page just as you describe, going back, and I often have to go a ways down before I'm sure whether "I've seen that!" to the top one means I'm caught up, or means it scrolled. And I don't even sub high-volume communities, but I do have a toddler and get distracted.
Also? My iPhone often refreshes pages when entering/leaving the browser, and can only have 8 open at once. This would let me actually READ my reading page on my iPhone, knowing that (after the first 20, anyway) if I went back it would pick up the "real" next 20 and any refresh would end up with the same result (because it'd have a start id, not a skip=whatever).
Oh please YES. I only wish I could vote for "should be implemented as is, and forced into the LJ codebase"....
no subject
Please please YES please.
I read my reading page just as you describe, going back, and I often have to go a ways down before I'm sure whether "I've seen that!" to the top one means I'm caught up, or means it scrolled. And I don't even sub high-volume communities, but I do have a toddler and get distracted.
Also? My iPhone often refreshes pages when entering/leaving the browser, and can only have 8 open at once. This would let me actually READ my reading page on my iPhone, knowing that (after the first 20, anyway) if I went back it would pick up the "real" next 20 and any refresh would end up with the same result (because it'd have a start id, not a skip=whatever).
Oh please YES. I only wish I could vote for "should be implemented as is, and forced into the LJ codebase"....