Actually Jerboa rewrites all http links to https. Originally it was because of cleartext, it wouldn't load http images. But then I decided all links should be rewritten to http for security. If it might be too troubling I could change this but imo all sites should support https

Jerboa forces HTTPS for images (Markwon plugin) because android doesn't allow to load http due to cleartext. I can disable this for older Android version but not in newer Android. There is a good reason for this as its much less secure. So instead I chose to rewrite http to https for links in markwon

https://developer.android.com/privacy-and-security/risks/cleartext

What's a wrapper in this context?

An app that's just WebView?

I did and i can click the title or the empty space in footer to open the post. But we can always add such button.

Can you not click anywhere outside the image? The title and white space should open up the post?

Voting gestures have been made opt in.

Jerboa doesn't have it yet but it's on the backlog

As in Lemmy deprioritizes it? It definitely doesn't, you can always change ur user agent to chrome. Would make it pretty much impossible detect it.

That was solved in 0.0.62

Yeah I manage to reproduce it, I'll fix it by next release.

The small font for tabs is a bug, and not intentional design.

That's not intended, what android version do you experience this?

This is expected atm, it is a webm video. Which isn't supported yet. Videos in general still need to be supported in Jerboa. But in the next update you will be to see first frame of the video (In the comments). (Ain't much but its better than nothing atm)

Maybe lemmy was having some issues?

Which upload succeded then?

Wym same error? I meant the above picture that uploads fine. Does it still work after you move it to the location of the picture that doesn't work.

By default it saves the picture in location that should always be accessible by Jerboa

It is very possible that we don't properly handle it when it fails to receive permission. I'll take a look at it.

That shouldn't be a problem, pictrs shouldn't be looking at the metadata.

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.

If this image uploads it's probably something else

Maybe we can look into changing the default.

Do any like the swiping gestures? They need some finetuning.