News for hackers. Stuff that matters.
Re:Infinite Scrolling: When to Use It, When to Avoid It by seydor on Saturday September 10, 2022 @09:57AM (#32790681)
even if the website did re-start where you left off (difficult), what if you scroll backwards? When you send a link, should it point to the page that you scrolled to, or to the beginning of the list? How many items before/after should load? These arise solely because people chose to reinvent a browser -in-the-browser. With pagination we dont have these issues, the link points to a specific results page, uniquely.
Re:Infinite Scrolling: When to Use It, When to Avoid It by marginalia_nu on Saturday September 10, 2022 @11:01AM (#32791224)
You can still have weird issues with pagination if the data set you're paging through is mutable.

Reddit used to struggle with this back in the day. The way they did pagination was to say "show the next page after id postId=xyz123". Since the algorithm kept re-sorting the posts on the front page, the content moved around quite a lot and you'd see the same things re-appearing on page after page, and sometimes post xyz123 was deleted and then everything broke.

Re:Infinite Scrolling: When to Use It, When to Avoid It by spookthesunset on Saturday September 10, 2022 @11:28AM (#32791495)
Infinite scroll or not you’ll have this problem on a mutable set of items. You’ll have to dedupe the next “page” either client side or server side. Or something!

It’s one of the reasons that the “I can build XYZ app in a weekend” crowd sounds so silly. I bet Reddit spent dozens of not hundreds of man-months nailing their scrolling behavior. It probably took many iterations of UX, product and engineering to get it right. And even now I bet they have a pile of JIRA tickets buried in their backlog relating to the pagination system.

In my experience there is a non linear relation between the more seemless and “easy” something appears and the amount of work that went into it. Things seem “easy” because the developers poured a pile of fit & finish on the system.

Re:Infinite Scrolling: When to Use It, When to Avoid It by Zak on Saturday September 10, 2022 @06:44PM (#32795160)
IIRC the first version of reddit and the Python rewrite were each more or less built in a weekend. They were neither scalable to millions of users nor heavily optimized to keep users on the site as long as possible.

The latter point is relevant to a variety of UX decisions across many products and services. Making it easy, efficient, and pleasant for the user to do what the user wants may not be the overriding concern in the design.

Re:Infinite Scrolling: When to Use It, When to Avoid It by marginalia_nu on Saturday September 10, 2022 @11:39AM (#32791582)
I'd note that Hacker News doesn't have this problem.

Although Reddit's design decisions are almost certainly to accomodate their much larger scale.

Re:Infinite Scrolling: When to Use It, When to Avoid It by krapp on Saturday September 10, 2022 @11:45AM (#32791658)
Infinite scroll isn't really useful in a low velocity environment like Hacker News, hot threads being the exception.

Hacker News being designed to display trees sorted by karma also makes it difficult, you would have to re-sort the entire page to re-rank every new subtree within the current display.

Apparently, this also makes pagination difficult, since pagination is implicitly chronological - what people want from pagination is to easily find the latest items - which karma sort doesn't allow.

Re:Infinite Scrolling: When to Use It, When to Avoid It by Wowfunhappy on Saturday September 10, 2022 @11:41AM (#32791606)
I've seen the problem on Hacker News. A story which was at the bottom of my page 1 is also at the top of my page 2.
Re:Infinite Scrolling: When to Use It, When to Avoid It by marginalia_nu on Saturday September 10, 2022 @12:00PM (#32791805)
Yeah, that's fine I think. I mean the problem of the pagination "crashing" due to removed posts.