Timeline pagination breaks when the last post in a page is a reblog #174
Labels
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: shadowfacts/Tusker#174
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.
Haven't seen this since, even with pleroma. Assuming this was a fluke