So.. I'm not crazy! I'm not the only one!
this post was submitted on 17 Jun 2023
21 points (100.0% liked)
Jerboa
10306 readers
1 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
- Open source, AGPL License.
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
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK - ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01 - monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV - cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
I could be wrong but I think the first click works, there's just no loading indicator, so then you click a second time because it's unclear if anything is happening, and then shortly afterwards the successful response from the first click comes back and it just looks like the second click did something.
These seems so simple but could be a manageable fix if it is that straightforward
The simplest standard fix is to just immediately start a loading spinner that disables the button until the first request comes back or times out, then at least the user knows that something is happening. Some sites use optimistic updating though where they just assume the request will be successful, benefit being that the change happens as soon as the user clicks the button but the downside is that it may change later if the request happens to error out for some reason.
Pretty sure this is an issue with Lemmy in general and not Jerboa. This happens on desktop, but weirdly not with all instances.
sometimes it also happen on the website (at least for me) so I don't think it's some jerboa bug, also note that this app is not even in beta at the moment, just give it some time.
I have found that for me it is only lemmy.ml communities. When I was on lemmy.ml it always happened. I moved to lemmy.world and now it is only lemmy.ml communities that do it. Desktop or mobile. It's an instance problem, not a jerboa problem from what I can tell.
This happens to me on lemmy.world as well, not using the app, curious that your move fixed it though. I think it might be a general lemmy issue rather than instance specific
I get it EVERYWHERE. Beehaw Lemme. World Lemme. Ml
It's a jerboa bug. Is it reported yet?
I think it does send the request the first time you click, but it takes a while to get a response from another server. Try it with some communities that are local to your server and you'll notice it's not so much an issue. I'm not a Dev and not am authority on the topic, but I think it puts your request into a queue, this helps make sure that your request makes it to the requested server in the case that one of those servers is temporarily down for maintenance or updates.
What I think needs to happen is just to provide a visual response to indicate that your request is sent and awaiting a response, which doesn't usually happen until you click it a second time.
Same.