active

Jerboa@lemmy.ml – 70 points – 1 years ago

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.0.36 on Android

Under settings, for my profile it has it set to All+Active, and will not keep any changes saved. I can hit the save button, and the settings won't save it i back out of that settings section and come back

--Update So if I go under settings and change the default filtering, save, THEN force close, THEN it updates to my preferred filtering. But if I want to change it again, then I have to go to settings and force close

I've noticed this too. You can work around it by updating your default sort in settings, save settings, and then close the app. when you reopen the app, your sort will be updated. It's annoying but hopefully will be fixed in 0.37.

Listen to this person, this is the temporary solution.

This is working for me, too. Just make sure you scroll down and hit the Save Settings button. I missed that the first time.

For me, it's only Local > Active that's showing.

Same. Which is like the worst possible sort option!

From what I can tell it just gets stuck on your default sort mode, for example I can't switch off of Subscribed+Hot

Is there a GitHub issue to track this?

Same, can't switch off Subbed/Active(or hot idr).

A reinstall fixed this for me, but broke my ability to subscribe to communities and post comments.

Edit: After a bit of browsing it broke again and now I can't subscribe and comment AND rearrange the feed.

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.

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

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

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.