322
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Dec 2023
322 points (99.1% liked)
Meta (lemm.ee)
3473 readers
3 users here now
lemm.ee Meta
This is a community for discussion about this particular Lemmy instance.
News and updates about lemm.ee will be posted here, so if that's something that interests you, make sure to subscribe!
Rules:
- Support requests belong in !support
- Only posts about topics directly related to lemm.ee are allowed
- If you don't have anything constructive to add, then do not post/comment here. Low effort memes, trolling, etc is not allowed.
- If you are from another instance, you may participate in discussions, but remain respectful. Realize that your comments will inevitably be associated with your instance by many lemm.ee users.
If you're a Discord user, you can also join our Discord server: https://discord.gg/XM9nZwUn9K
Discord is only a back-up channel, !meta@lemm.ee will always be the main place for lemm.ee communications.
If you need help with anything, please post in !support instead.
founded 1 year ago
MODERATORS
After the lemm.ee server upgrade (excited!), when I scroll past the first loaded Subscribed "page" in the Jerboa app, it provides a "Posts failed loading, retry" message. It seems to dynamically load multiple pages for "Local" and "All" just fine. I have no idea if this is a server/lemm.ee or client/Jerboa issue, just wanted to see if anyone else has seen a similar problem or has ideas to fix. Thanks.
Could you check if you can reproduce this in the web browser at https://lemm.ee ?
Seems OK via the browser (hit next to load a few pages). Might be the app, or the Jerboa app (0.0.52) interacting with the new server weirdly? I may try a full re-install just to be thorough.
Edit: tried a full uninstall, reinstall, and login. Same issue on my end. I suppose it may be better to try and attack this from the Jerboa side.
Log out and back in
I had to log out and back in yesterday after the server upgrade. For good measure, I just logged out, cleared cache and data for the app, and logged back in again, and am still experiencing the same problem.