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.
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.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutmFiskFisk23 and my comment are both replies to Botree's comment, it gets even more confusing when tapping Show context a second or third time.
Just considering raising a bug report with the same issue.
I've seen this, too, and was quite confused until I realized what was going on. It's not site-breaking for me, but I do find it odd.
It probably happens because in this case, the child comment is the "center" of the comment tree, and the dev may have wanted to present it's parent as a tree going the opposite direction. But it is confusing.
I must be in the minority here because this is virtually site-breaking. Whatever broke this should have been rolled back immediately.
I logged in after a few days to about 20 replies and had no easy way to tell what comment of mine people were replying to. I gave up searching after a while.