Is anyone having issues with nested replies not showing up as nested?

0x4E4F@lemmy.rollenspiel.monster to Jerboa@lemmy.ml – 26 points –

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.

17

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.

I'm seeing the same bug, and I don't see a github issue for it. Wanna create one?

No need to create an issue, it's a BE (backend) bug, fixed in 0.18.4, but our instance admins haven't update to the latest BE version ๐Ÿคท.

I appreciate your commitment to informing folks about the bug being with lemmy once you learned the details :)

Which Jerboa and Instance backend versions are you seeing this with? There was an issue in the backend that could produce this behavior but should be fixed in 0.18.4: https://github.com/LemmyNet/lemmy/pull/3823

BE of my instance: 0.18.3.

Then ask your instance admin to update to 0.18.4. I don't see this bug using the same Jerboa version on my home instance, which has already updated.

Yeah, that should be super easy, since In don't speak any German ๐Ÿ˜’.

Nevertheless, I'll try and see if they reply.

0.0.42... that's the version in the About section.

BE of my instance?

Yes, when you open the homepage of your instance in a browser and scroll to the bottom, it should say something like "BE: 0.18.4".

If it says that and you still get this bug, it's a new one.