If you can code, https://github.com/dessalines/jerboa/blob/main/app/src/main/java/com/jerboa/ui/theme/Color.kt

It is possible for someone to make a theme like that.

The pull to refresh is currently too sensitive on big screens (tablets) to pull down or not sensitive enough on smaller screens it seems. We are just using default implementation of it.

There is a new PID for each new execution of any app. On device restart most logs go away from experiences just the error levels ones remain for some time.

Make GitHub issue with full logs

The API endpoints? It is instance/api/v3/user/unread_count?auth=TOKEN And this instance/api/v3/private_message/list?page=1&unread_only=true&auth=TOKEN

This is definitely a bug, can you make an issue on github for it.

There is a button to mark as read, aswell a mark all as read button.

It’s just hasn’t been added yet. For that feature it would have to continuously poll in some interval in the a background for each account. Since the websocket API is removed.

It does since 0.40

Its a bug where it fails retrieving the account info, it makes it look like ur not logged in. It’s more notable recently because instances are having more issues.

Not a Jerboa specific issue

Could you make an issue with the full logs on github?

It’s because Jerboa thinks it’s a community bc of the /c/. There is a fix already for this in works and should hopefully be in the next release

There is a PR in works for that and that one allows you to disable it too.

Strange I just tried reproducing this but i was unable to do so. Does it only happen in Jerboa? Maybe a powersaving feature of your device is causing it. I think I might have idea to fix this. You will have to make an issue on github with your specific device and anything relevant. And then I can send you some test builds to see which resolves it.

That’s a lemmy bug, nothing to do with Jerboa.

See https://github.com/LemmyNet/lemmy/issues/3588

Deletes are not being federated

That button has never done anything, it’s functionality has yet to be implemented. There is draft in working, when ever that gets finished it will be in Jerboa.

test !linux@lemmy.ml

The navigation buttons resetting the navigation History is currently the intended behavior and not a bug. I am adding a back confirmation feature, that should be in 0.39 or 0.40. If more users prefer it not to do the nav resetting, i suggest making a issue to amend this, so that we can properly weigh in the desired behavior by the majority of the users.