this post was submitted on 09 Aug 2023
26 points (100.0% liked)

Jerboa

10270 readers
2 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
dessalines@lemmy.ml
26
Is anyone having issues with nested replies not showing up as nested? (lemmy.rollenspiel.monster)
submitted 1 year ago* (last edited 1 year ago) by 0x4E4F@lemmy.rollenspiel.monster to c/jerboa@lemmy.ml
17 comments fedilink hide all child comments
 

The title. Basically, when I look at the replies (notifications) and I tap to see where that reply is, the nest comment sort is reverse 🤨, and in some cases, not present at all (it shows up as a new comment in the post, but in fact it's a reply to my comment).

If you just look at that post and comments in "normal mode", everything's fine, no reverse nested order of comments. I've noticed this problem only shows up when viewing replies, but only if you follow (tap) on the links from Notifications.

EDIT: To everyone reading this, this is not a Jerboa bug, it's a backend bug (BE). Instances that have BE version 0.18.4 don't have this bug... so, we have to bug our admins to update the BE.

you are viewing a single comment's thread
view the rest of the comments
[–] bionicjoey@lemmy.ca 5 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah I've been seeing the "reversed" comments as well. It shows only when I click a link to a comment which is deeper down a comment chain (eg. Clicking a comment from my profile and looking at the replies)

Edit: lemmy.ca got updated and it's back to normal now.

[–] 0x4E4F@lemmy.rollenspiel.monster 2 points 1 year ago

It's a BE (backend) bug. Our instance admins need to update the BE to version 0.18.4.