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.
It is a kbin server, and you’re speaking to the admin🙂. (Replying to @[email protected] as well). Both jpgs are the full size images, not thumbnails. There is no imageviewer, I’ve disabled it because it had trouble displaying on Iphones and zooming issues on other mobiles. So, when you call the url, you get the raw 33MB jpg. So I’d think it should be possible to display it as is?
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.
Oh, misunderstood you there, my bad. Hope you can figure it out. Could you check for me if another kbin instance, on another channel with images, does give you two urls though? I’m curious if it’s supposed to be like this (2x same url)
They all seem to have the same url & thumbnail_url, except for #9, which has a thumbnail on lemmy.world. Makes me wonder why that one does and all the others don’t
This is interesting now that I’m thinking about it. if you get the same from another instance, are the thumbnail and regular url different? The fact that the viewer is disabled my side should not influence the actual uris presented to the outside world, I’d think.
You are opening the actual kbin instance it seems, not browsing it through the app
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.
Yes, it’s opening thumbnails instead of the actual images. The actual images are >20mb in size and very high detail (and take much longer to load)
The thumbnail is the same as the url, I think this a deeper issue with the imageviewer
It is a kbin server, and you’re speaking to the admin🙂. (Replying to @[email protected] as well). Both jpgs are the full size images, not thumbnails. There is no imageviewer, I’ve disabled it because it had trouble displaying on Iphones and zooming issues on other mobiles. So, when you call the url, you get the raw 33MB jpg. So I’d think it should be possible to display it as is?
Oh, you are the admin? LOL, well kick me in the balls and call me Shirley, didn’t know, my bad. 😂
Surely!
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.
Judging by the time it takes to download the pictures (after clearing the app cache) I’d say the full pictures are indeed downloaded
Oh, misunderstood you there, my bad. Hope you can figure it out. Could you check for me if another kbin instance, on another channel with images, does give you two urls though? I’m curious if it’s supposed to be like this (2x same url)
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
They all seem to have the same url & thumbnail_url, except for #9, which has a thumbnail on lemmy.world. Makes me wonder why that one does and all the others don’t
https://imgur.com/a/yUOCKbo 😀
Nice work! What was the cause?
This is interesting now that I’m thinking about it. if you get the same from another instance, are the thumbnail and regular url different? The fact that the viewer is disabled my side should not influence the actual uris presented to the outside world, I’d think.