Timeline pagination breaks when the last post in a page is a reblog #174

Closed
opened 2022-09-15 17:26:06 +00:00 by shadowfacts · 2 comments
Owner

i think we're generating new pagination params by looking at the id of the last status in the page, but that breaks if the last one is a reblog because we end up using the id of the reblogged status rather than the reblog itself

this results in big discontinuities scrolling back through the timeline if there's a reblog in the wrong place

i think we're generating new pagination params by looking at the id of the last status in the page, but that breaks if the last one is a reblog because we end up using the id of the reblogged status rather than the reblog itself this results in big discontinuities scrolling back through the timeline if there's a reblog in the wrong place
shadowfacts added the
bug
label 2022-09-15 17:26:06 +00:00
Author
Owner

Not sure if that actually fixes it. I'm beginning to think this might be a pleroma bug, because we're definitely not using the reblogged status' id for pagination. Maybe pleroma's pagination headers will return something different that avoids it, or this bug has always been present and I've just never noticed it.

Not sure if that actually fixes it. I'm beginning to think this might be a pleroma bug, because we're definitely not using the reblogged status' id for pagination. Maybe pleroma's pagination headers will return something different that avoids it, or this bug has always been present and I've just never noticed it.
Author
Owner

Haven't seen this since, even with pleroma. Assuming this was a fluke

Haven't seen this since, even with pleroma. Assuming this was a fluke
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: shadowfacts/Tusker#174
No description provided.