Public
Federated
Thread
How to improve my fedi experience tenfold:
clone the bloatfe pagination links to the top of the page, append a hash with "bottom" to [prev] links, and have the browser scroll to the bottom if it's got the bottom hash.
(I was gonna use the actual hash string, but that'd probably be a bad idea.)

replyReply to @[email protected]
@e@anime.website Is it
1. Move pagination links to the top
2. Start at bottom on "prev" page
Or something else?
replyReply to @[email protected]
@r@freesoftwareextremist.com both
the navigation links are just copied to the top though, not moved

replyReply to @[email protected]
@e@anime.website That would look a bit weird but kind of makes sense for the prev link. Not sure if it's still worth it though. About the scrolling part, it only takes one keystroke to move to top/bottom of a page, but it's not so easy to focus/scroll to a particular part of a page, which is why it uses URL fragment to focus a status div on certain pages. next/prev pages on the other hand are just regular pages, there's nothing to focus on them, scrolling to bottom with a hash would just be a dumb hack (yet useful in this case). Do share the patch though, if it actually feels worthwhile, then maybe I'll merge it.
Also, at one point, I considered removing the prev link altogether because of this issue: https://git.pleroma.social/pleroma/pleroma/-/issues/2431 . Currently there's no way to know whether there's any previous content or not. Initially bloat used to make another call to the server to check for the previous and would only show the prev link if it gets anything in the response. The second API call is now removed and now it shows a prev link if there's any min_id/max_id pram passed in the request, which is very unreliable, but there's no better option. It's the reason why there are no prev links on any other pages besides the timeline page.
@hyphen@anime.website

Do not generate `rel=next` in the Link header when there are no more records (#2431) · Issues · Pleroma / pleroma · GitLab
The issue was originally described in https://patch.cx/notice/A3InRXBfh6SMFMuZsW . Currently Pleroma just generates rel=next header regardless of whether there are any...