i am filtering almost 50 instances and a lot of communities and have multiple keyword filters. when i decide to browse ‘all’ in new i get this error after a while: even if i try to browse ‘old’ or ‘active’ still get the same issue. i have mark scrolled posts as read and hide read posts toggles on, if that info is of any use. also i dont get posts too on the sync app when having the same amount of filters. should i spin my own instance ?
Hi, I think this is caused by a couple things. Lemmy has a ratelimit on the number of API requests you can send and also marking posts as read and a lot of filters cause the app to pull more since some content gets filtered out.
I think a possible solution from my side might be instead of sending the read calls right away (so quickly scrolling past everything will send a lot of API calls quickly) would be to queue them and release it in chunks.
man i am really looking forward for ur optimizations! i really like to scroll endlessly and discover the lemmyverse (filtering lemmy.world already, which occupies most of the ‘all’ feed, eclipsing all the small and quircky instances out there) i would really consider a donation if this is gets sorted out, and as always, i advocate for Connect wherever i go! really, Thank you :)
onegai dev senpai @[email protected] 😭
