tapping home scrolls to the top when you are at home
tapping home scrolls to the top when you are at home
? You can’t use the same strategy for what u do to find communities. (assuming you use the name field to retrieve the community) there is no equivalent
How are you gonna implement saved/banned content replication? Alls ids for posts are local to that instance, how are going to find one post from on instance in another. It might not even exist yet.
What happens if you try to swap? I don’t know what happens with a banned account.
Can you not swap to that account and sign out?
What sidebar, your account list?
In what way? It uses M3 ?
Jerboa does not delete your account when it fails to reach the instance. Instead when it fails to retrieve your profile it falls back, to the defaults which is displaying the anon account.
I have a fix for this, and many other checks. But it still needs to be reviewed.
As the others said simply restarting the app makes another attempt.
btw your suggestion is already included in that PR
For only that post it has the same two urls, the other posts seem indeed to have a different url
You can see the links here: https://lemmy.world/api/v3/post/list?community_id=86965&page=1&sort=Active
I am aware, and I am talking about the imageviewer in Jerboa, which I wrote. Currently Jerboa uses default jetpack compose image with CoilImage painter and some 3rd partylib to allow zooming. CoilImage does downsampling (reduces the pixels to increase perf when you can’t see it anyway). During the zooming is probably where it goes wrong and it should load a higher res version. I’m pretty sure it actually loads the full image but I have not confirmed that yet.
The thumbnail is the same as the url, I think this a deeper issue with the imageviewer
I’m sorry, I’m not exactly understanding the problem yet. In the gif i can see you open the images. Is the problem that u open the lowres thumbnails and not the actual images? Bc I don’t think it does that. I did notice there is apparently a limit to zooming into a image.
Works perfectly fine for me?
Honestly I have never experienced this. Does it happen with specific images or is it just random? What version are you using, 0.44?