reply on: How does the "endless feed" work? Is there a way to block it across all apps? \ stacker news ~devs

pull down to refresh

112 sats \ 1 reply \ @ek 22 Mar \ on: How does the "endless feed" work? Is there a way to block it across all apps? devs

Using the Intersection Observer API is one way:

The Intersection Observer API provides a way to asynchronously observe changes in the intersection of a target element with an ancestor element or with a top-level document's viewport.

Historically, detecting visibility of an element, or the relative visibility of two elements in relation to each other, has been a difficult task for which solutions have been unreliable and prone to causing the browser and the sites the user is accessing to become sluggish. As the web has matured, the need for this kind of information has grown. Intersection information is needed for many reasons, such as:

Lazy-loading of images or other content as a page is scrolled.

Implementing "infinite scrolling" websites, where more and more content is loaded and rendered as you scroll, so that the user doesn't have to flip through pages.

I think infinite scroll should at least be opt-out.

0 sats \ 0 replies \ @Signal312 OP 23 Mar

If they allowed you to opt out, then lots of people would, and their "engagement" would be lower.

I wonder if you could fake out the site...have some kind of extension that puts a bunch of empty lines at the bottom.

Then, because (according to AI, anyway) they're using some kind of scroll event listener to detect when the user is at the bottom of a page....the user would just not GET to the bottom of the page, and the page wouldn't know to load more items.