Live data from Hacker News

The infinite scroll may become endangered if controversial Calif. law passes

sfgate.com

31–40 of 464 posts

Re: The infinite scroll may become endangered if controversial Calif. law passes

#31
post #29

Earlier quoted context omitted.

Infinite scroll evolved alongside algorithms that incentivise addictive content. So it’s “good” UX in that it’s effective for consuming addictive content… When I’m trying to do something constructive, like search or browse, infinite scroll is IMHO disastrously bad. You can’t keep your place in the list, or jump ahead/back.

On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.

Why is the list constantly changing anyway?

Re: The infinite scroll may become endangered if controversial Calif. law passes

#32
post #29

Earlier quoted context omitted.

Infinite scroll evolved alongside algorithms that incentivise addictive content. So it’s “good” UX in that it’s effective for consuming addictive content… When I’m trying to do something constructive, like search or browse, infinite scroll is IMHO disastrously bad. You can’t keep your place in the list, or jump ahead/back.

On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.

‹looks at hn›

Re: The infinite scroll may become endangered if controversial Calif. law passes

#33
post #31
post #29

Earlier quoted context omitted.

On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.

Why is the list constantly changing anyway?

Because other people keep adding new posts (and upvoting existing posts, which changes their order).

Re: The infinite scroll may become endangered if controversial Calif. law passes

#34
post #29

Earlier quoted context omitted.

Infinite scroll evolved alongside algorithms that incentivise addictive content. So it’s “good” UX in that it’s effective for consuming addictive content… When I’m trying to do something constructive, like search or browse, infinite scroll is IMHO disastrously bad. You can’t keep your place in the list, or jump ahead/back.

On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.

The challenge is to retain an ordering over the result set. How would infinite scroll behave any differently in this case? The changing results seems to be an orthogonal concern to pagination/infinite scroll.

Re: The infinite scroll may become endangered if controversial Calif. law passes

#36
post #29

Earlier quoted context omitted.

On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.

The challenge is to retain an ordering over the result set. How would infinite scroll behave any differently in this case? The changing results seems to be an orthogonal concern to pagination/infinite scroll.

Infinite scroll makes the problem much easier, even if it’s still a problem. The only action you need to support is loading more results, which you can do by loading all results and filtering out those already shown. With pagination, the user may say “give me page 3” and you have no idea what was on pages 1 and 2, if they were even loaded.

Re: The infinite scroll may become endangered if controversial Calif. law passes

#38
The problem with infinity scroll is the lack of "pagination", which essentialy make most of content to get hidden away. For instance. Let assume you have 3000 comments on a YouTube video, your browser will crash way before it "infinite scroll" to the end (I know that that are tools to bypass this, but I'm talking about the default experience).

Re: The infinite scroll may become endangered if controversial Calif. law passes

#40
I (personally) think this is the wrong kind of solution.

I think a better solution would to mandate that platforms offer a ranked feed and a chronological feed and make the setting sticky for users.

I think giving users the agency over how much they consume is good but mandating a “UX” pattern feels too specific.

Post reply on HN