Usually when I reach the end of the feed, it just loads more. But recently, I started getting a bad request error instead. Not every time I reach the end, but once I get it it doesn't go away when I tap on retry.
Is anyone else seeing this happening? Is there anything I can do to fix it?
Sorry for the late update, just got back from break. I think I posted this somewhere else but I'll re-iterate here as well. Basically this is a limitation on the server side when page indices are used instead of cursors. I specifically chose to implement Summit using page indicies instead of cursors because (1) page indices are more feature rich and (2) it results in cleaner and more maintainable code on the client. Cursors has several limitations such as the inability to go to the previous page. Lemmy is also very inconsistent as many endpoints only support page indicies and not cursors. This means that if I were to support cursors I would have to write two different pagination implementations.
That being said, due to the issue of servers now limiting the max page index to a low number like 10, I will likely be forced to implement cursors on the client. I'll work to implement this for the next release since this is a pretty big issue.