Might be that there’s some way of blocking that behavior if you don’t like it, though, if I’m not seeing it.
Not without either breaking most SPAs (Single-Page Applications) or writing userscripts with site-specific logic.
The classic way of doing this crap was to make a placeholder page navigate to the article page. That leaves the redirect page in the history stack so when the user presses the back button, it just opens the page that navigates them forward again.
The modern way is to use the history API with history.pushState to add a history entry while listening for the popState event to check if the user pressed the back button. Unfortunately, both of those features have a legitimate use case for enabling navigation within a SPA.
zipzoopaboop@lemmynsfw.com 23 hours ago
Might be a b testing