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?
I’m seeing this too, @flamingos@feddit.uk reckon it’s anything on our end?
I can recreate this, the error I’m seeing on the server side is
Page limit is > 10. I wish client side gave a better error message here thancounldnt_get_posts.This seems to have been a deliberately changed in this PR to fix comment list sorting DDOS exploit. How this affects clients depends on if they use
pageorpage_cursor, which has no limit.For now I’ll just patch our Lemmy to increase to increase the limit to something more reasonable, like 100. Probably need to upstream this as well as it’ll affect every instance on
0.19.14.Thanks both @smeg@feddit.uk and @flamingos@feddit.uk! I assumed it was an issue with summit so posted here, didn’t realise it was an issue with the instance
Likely is. I’m experiencing something similar with timeouts instead, but it happens across clients (and less often since a server upgrade). So probably a change in configuration for your instance, or an uptick in usage/growing userbase?
Either way I’d check to see if this happens on other clients too, first.