this post was submitted on 15 Dec 2025
8 points (100.0% liked)

Summit

1194 readers
2 users here now

Community to discuss Summit, an open-source Lemmy reader for Android.

App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit

APK: https://github.com/idunnololz/summit-for-lemmy/releases

Source: https://github.com/idunnololz/summit

Support the app

Support me on Patreon

Website: https://summit.idunnololz.com/

founded 2 years ago
MODERATORS
 

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?

top 9 comments
sorted by: hot top controversial new old
[–] smeg@feddit.uk 2 points 1 week ago* (last edited 1 week ago) (2 children)

I'm seeing this too, @flamingos@feddit.uk reckon it's anything on our end?

[–] flamingos@feddit.uk 5 points 1 week ago* (last edited 1 week ago) (1 children)

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 than counldnt_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 page or page_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.

[–] theOneTrueSpoon@feddit.uk 4 points 1 week ago

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

[–] dabaldeagul@feddit.nl 3 points 1 week ago

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.

[–] Bubs@lemmy.zip 1 points 1 week ago* (last edited 1 week ago)

I've been getting the same for maybe 2/3 weeks now. Quite frustrating because I'm missing a lot of posts and keep getting repeat posts all the time. Plus, sometimes the app just refuses to download images to my phone.

I would hate to leave summit over this, but it's really making Lemmy unusable.

[–] limerod@reddthat.com 1 points 1 week ago* (last edited 1 week ago)

I have been getting 400 bad request error in comments, in URL preview of opened posts. I guess something is on summits end. Because, these errors are less frequent in Voyager and its very quick I operation.

[–] rescue_toaster@lemmy.zip 1 points 1 week ago

Yeah this has been occurring for me as well. It's getting frustrating. Would hate to switch to another lemmy app as otherwise I really enjoy summit.

[–] theOneTrueSpoon@feddit.uk 1 points 1 week ago (1 children)

@idunnololz@lemmy.world just making you aware of this

[–] idunnololz@lemmy.world 3 points 1 week ago

This might have to do with the user agent issue. I'm planning to do a release tomorrow to fix this.