It’s a BE (backend) bug, so it’s not Jerboa related. Our instance admins have to update the BE to 0.18.4.
It’s a BE (backend) bug, so it’s not Jerboa related. Our instance admins have to update the BE to 0.18.4.
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 🤷.
It’s not a Jerboa bug, it’s a BE bug, confirmed a few posts below. Lemmy.ml should be on 0.18.4, so should lemmy.dbzer0.com.
Yeah, that should be super easy, since In don’t speak any German 😒.
Nevertheless, I’ll try and see if they reply.
BE of my instance: 0.18.3.
0.0.42… that’s the version in the About section.
BE of my instance?
I’ll create one 👍. Just need more confirmations, a few more replies should do it.
It’s 2 devs actually, but still, a lot of workload for just 2 guys… sure, they have help with the sudden influx of users, but that doesn’t change the fact that they have to review PRs before they’re submitted to main/master.
OK, so things should improve with time, that’s good 👍. And yeah, I was talking about using it on a phone, I don’t own a tablet.
Well… it’s OK, but the scroll features in Jerboa are kinda… choppy and not always working as they should. And about the scroll to refresh, you have to like realy pull waaaay down.
Still, I would say the shortcut to reload the feed (whether it be long tap or double tap, whatever) is completely optional, but I would like a shortcut to at least scroll back up to the start of the feed without having to go into menus.
The hamburger menu is on the left, that’s the three dot menu in the upper right, but thanks, that helps 😉.
Yeah, you’re right, that is quicker 🤦 😂.
Latin as in the Latin keyboard 😒.
No, it does reset the feed to the beginning. And yes, it shouldn’t do that the first time you hit the home button if switching from something other in the bottom menu (search, messages, whatever). The second time you tap it (or if already in home), yes, it should scroll you back to top.
Or at least that would be my logic, how I would set it up.
It’s a BE (backend) bug. Our instance admins need to update the BE to version 0.18.4.