this post was submitted on 28 Jun 2023
76 points (100.0% liked)

Jerboa

10295 readers
13 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
76
Jerboa only sorting by All+Hot ? Can't change to subscribed/local or any sorting types like new/new comments/active (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by TheAmishMan@lemmy.world to c/jerboa@lemmy.ml
20 comments fedilink hide all child comments
 

As the title says, I can't change from All+Hot. I at best can go to specific communities, but can't filter to only subscribed or local (i really don't understand who wants local only, but whatever). On version 0.36

you are viewing a single comment's thread
view the rest of the comments
[–] FortaDragon@lemmy.world 5 points 1 year ago (3 children)

I'd figured this was part of the whole 0.17 vs 0.18 thing Jerboa and lemmy.world have going on, and that's why it wasn't widely complained about.

[–] MrNemobody@lemmy.ml 4 points 1 year ago

No, I'm in lemmy.ml and I still face the same issue...

[–] TheAmishMan@lemmy.world 2 points 1 year ago

I wasn't sure if that was the issue or not, but I swear at one point it was working on 0.0.36 even with lemmy.world being on 0.17

[–] sugar_in_your_tea@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago)

Kind of, but it's pretty much entirely Jerboa's fault. There was a pretty big refactor in the code to support 0.18 (Jerboa now uses automatically generates the API interaction code), so the next big change should be smoother.

There was another big change internally after 0.0.36 I think, and that one should fix a lot of these issues, but it could cause more. I'm trying to test on the latest development head to find bugs before 0.0.37.

Anyway, I'm hopeful that we'll have fewer of these types of bugs (ones where settings aren't consistently honored) in the future.