I think they meant how you can’t get a permalink to your feed/timeline view-state[1], so other people can see exactly what you see (not just what’s in the viewport but also the surrounding/offscreen content and broader context).
[1]: something like a link specifying the contents of my feed at a specific date+time and scroll-position.
…whereas with old-school SSR paging it’s right there in the querystring paging params (page-size, page-index or item-offset, and an optional results anchor for stability).
I’ll concede that a well-designed infinite-scrolling (or “click to load more inline” button) feature could use history.pushState to dynamically update the browser’s address with new query params but I don’t think I’ve ever actually seen anyone do that - which is a shame.
alt Hacker News
I think they meant how you can’t get a permalink to your feed/timeline view-state[1], so other people can see exactly what you see (not just what’s in the viewport but also the surrounding/offscreen content and broader context).
[1]: something like a link specifying the contents of my feed at a specific date+time and scroll-position.
…whereas with old-school SSR paging it’s right there in the querystring paging params (page-size, page-index or item-offset, and an optional results anchor for stability).
I’ll concede that a well-designed infinite-scrolling (or “click to load more inline” button) feature could use history.pushState to dynamically update the browser’s address with new query params but I don’t think I’ve ever actually seen anyone do that - which is a shame.