Multiple Lemmy apps serve the first ‘page’ of posts fine - even new posts or updates - but upon scrolling and requesting the next page, Boost gives an error message “timeout”, and Blorp just doesn’t load anything else (per app implementation, I know).
It’s an older issue (from earlier this year) but I wonder I’d this bug is related. https://github.com/LemmyNet/lemmy/issues/5376
Anyone know what version sh.itjust.works is running?
According to the footer of the web interface, sh.itjust.works is running Lemmy 0.19.12 at the moment.
I am so glad someone mentioned this! The past 2 or 3 days this has been happening to me and I thought it was just on my end, I thought I was going crazy! Only happens on my mobile app. I am using the Jerboa app for reference. Perhaps an API issue? I am not sure. I recommend just using it on a mobile web browser using oldsh.itjust.works for the time being.
Edit: Use the alternative URL oldsh.itjust.works instead. The issue is not isolated to mobile apps, the page 2 timeout occurs to me only on the main sh.itjust.works site even on browser.
I also wanted to add my feedback, but life is always busy. I’ve been experiencing the timeout in boost on android for a few days across multiple internet connections, so I was pretty confident it’s not a ad block, vpn, content filter. Unfortunately it hasn’t made it to priority for me to track in any of my systems. I might be able to log and capture traffic is needed. I’m a network engineer with access to some enterprise grade network gear, unfortunately my primary desktop computer just died due to bad windows update, RIP last install. serving me well for many many years.
Blorp dev here. I would love to get this resolved. Could you be more specific?
- If you’re on the web: could you link the specific page(s) you are seeing this error on?
- If you’re on the app: which screens are you on (e.g. all feed, local feed, subscribed feed, a specific community feed)
It’s easier to debug things on web, and Blorp shares 99% of the code between app and web. So if possible, could you recreate the issue on web, and link that? Knowing what instance you’re using (I assume sh.itjust.works), is also helpful.
Edit 1: I saw you added a little more context in another comment. I’m having trouble recreating the issue on the all feed using sh.itjust.works. I see the first page of 50 posts loads, when I get to the bottom, it loads the next 50 posts and so on. Maybe describe exactly what’s happening in excruciating detail. It it slow? Does it never load? If you wait 60 seconds, does it eventually load? Are you using a VPN?
Edit 2: It seems others are getting this same error https://sh.itjust.works/post/43676767Just going to add myself to the group of people experiencing this issue.
This issue appears unrelated to the client as I see it in bothering jerboa and in web browser.
I have this issue too. Except for me the issue is only happening to me in Jerboa, but opening the site in a mobile browser allows me to go past the first page.
Are you logged in when you are viewing in the browser?
I just realized I normally use the oldsh.itjust.works to access this site and that works fine for me both logged in/out, but after trying the normal sh.itjust.works site I see the page 2 loading issue on desktop too now.
Seconded, using Jerboa

Huh, and this is specific to sh.itjust.works? That’s odd.
I’m not sure if that, sorry. That’s just my primary (?) instance, and I’ve seen it happen before and saw another post thinking it was the instance, too.
It might not be just the instance, since it only happens when aggregating ‘all’, and not local or subbed.
Bear with me. I’m a relative newbie to Lemmy & federation.
I’m having this issue as well, using both web and Voyager




