If this image uploads it's probably something else
testEmailVerified
Maybe we can look into changing the default.
Do any like the swiping gestures? They need some finetuning.
For Jerboa we usually do a weekly release. As far as I know we have had no problems yet
Btw how smooth/ fast is your IDE for multiplatform development? Android Studio for just android app is a bit slower than Intellji doing Java services. But my multiplatform ktor API using Intelji is sooo slow. Unbearable, can't wait until K2 mode drops
Relatively speaking there is lot of Lemmy clients compared to other (federated) social medias. Only mastodon comes near it.
I looked into it and the only thing I could find was some admin actions that also should be hidden for non admins.
I can successfully ban/unban from community as non admin mod.
These changes will land in 0.0.61
If you are able to reproduce this issue still in 0.0.61 please let me know
Thanks for your corporation!
No changes in 0.0.60 that affect moderation
If you disable the option to show the navigation bar. It will show the entries in the sidebar.
I assumed originally that is how you accesed that screen. But it seems that I was wrong. But that was a bug that I had to fix anyway.
It seems we don't properly filter these actions in the mod action menu either.
I'll take a look at that too.
Btw you can see the actual version of your app by going to Settings > About. Or by checking the relevant app store
I looked into it, you accessed these screens through the sidebar/drawer? Those weren't supposed to be visible for non admins as they are all admin actions
I'll take care of it
That was a bug in a lemmy 0.18.X, where it introduced sanitation against XSS. After XSS attack had happened. Which was introduced with the custom smiley feature, which allowed arbitary js to be executed on every client.
Which then was removed in 0.19. When I had discussion with the Lemmy devs that this responsibility lays on the clients to properly santize this. (Display text as text, fault layed in Lemmy UI)
There is a issue for that already
Hmm it could still be a permission issue but that would be on ourside to fix. Did you save this image in the same place as the others? If so can you try that. It might be that we don't ask correct permission on Android 13.