I can’t find related issues on GitHub, but it should be Lemmy’s behaviour. I don’t think dcx made any modifications to the source code, only deployed it using the provided Ansible script.
We can open a GitHub issue on their repository too, but I’m not sure which part is causing the issue(the UI or the image storing) as I’m not home rn. I’d figure it would be better if I can at least figure out where the issue came from before reporting it
Oh no, not the log files nightmare :( this shit was haunting even my company lol because we started adding new tools
But that part can be modified in the deployment script I think… I’ll take a look at the deployment scripts later.
Thanks, I’ll take a look at imagemagick too. I saw pict-rs yesterday but I haven’t looked up what’s that
Update:
I found this issue on magick’s github repo, but I can’t find something similar so maybe it’s missing a pictrs config, or pict-rs itself is having issues by maybe… not supporting -add-orient. :( Pict-rs is a rust service, so it’ll probably be harder for me to dig into that as I’m not familiar with it…
I’ll probably create a ticket for when I have time, need to finish up some IRL stuff and head to bed soon. Or if anyone wants to create the ticket also can
perhaps if we really want to dig into this issue, it could start with either preventing pict-rs from auto-converting to webp, or upgrading pict-rs to the latest 0.4.0?
I’m not sure if all images are stored as webp, because when I viewed the image in element inspector it showed up as jpeg(it either happens to all image extensions or images are stored on webp but converted to jpeg when displaying).
Thanks for sending the link, I didn’t manage to find this last night D: will take a look after work… I hope today no need to OT
Oh… So it really is the auto orient then! Thanks for your help, I’ll post a GitHub issue later on Lemmy’s repo later(maybe the Ansible one since that’s where the version is defined?) if no one else has done it yet.
Haha, yeah it auto landscape for portrait picture, dunno why.
@[email protected] is there a reason this happened? Or is it just lemmy jank?
uwu hi fluffy
I can’t find related issues on GitHub, but it should be Lemmy’s behaviour. I don’t think dcx made any modifications to the source code, only deployed it using the provided Ansible script.
Yeah, i tried posting portrait on lemmy.world and it auto landscape it too. So it’s lemmy jank
I haven’t read much of the source code(need some time to figure things out), but I hope I’ll find something eventually 🥹
Ohh man, thanks for the work!
We can open a GitHub issue on their repository too, but I’m not sure which part is causing the issue(the UI or the image storing) as I’m not home rn. I’d figure it would be better if I can at least figure out where the issue came from before reporting it
dont know if this is of any help, but from the docs I read, it seems lemmy is using pict-rs for image hosting, and pict-rs uses imagemagick.
since you mentioned the Ansible script, I took a look at its repo, and perhaps dcx may also want to watch out for this issue: https://github.com/LemmyNet/lemmy-ansible/issues/87
Oh no, not the log files nightmare :( this shit was haunting even my company lol because we started adding new tools But that part can be modified in the deployment script I think… I’ll take a look at the deployment scripts later.
Thanks, I’ll take a look at imagemagick too. I saw pict-rs yesterday but I haven’t looked up what’s that
Update: I found this issue on magick’s github repo, but I can’t find something similar so maybe it’s missing a pictrs config, or pict-rs itself is having issues by maybe… not supporting -add-orient. :( Pict-rs is a rust service, so it’ll probably be harder for me to dig into that as I’m not familiar with it…
I’ll probably create a ticket for when I have time, need to finish up some IRL stuff and head to bed soon.
Or if anyone wants to create the ticket also canAhh, interesting. Thanks for the work!
if anyone is familiar with rust (I am not), this should be the relevant code: https://git.asonix.dog/asonix/pict-rs/src/branch/v0.3.x/src/magick.rs (linking to the v0.3.x branch because that’s what lemmy-ansible uses).
perhaps if we really want to dig into this issue, it could start with either preventing pict-rs from auto-converting to webp, or upgrading pict-rs to the latest 0.4.0?
I’m not sure if all images are stored as webp, because when I viewed the image in element inspector it showed up as jpeg(it either happens to all image extensions or images are stored on webp but converted to jpeg when displaying).
Thanks for sending the link, I didn’t manage to find this last night D: will take a look after work… I hope today no need to OT
just saw that the latest 0.4.0 uses -auto-orient: https://git.asonix.dog/asonix/pict-rs/src/tag/v0.4.0-rc.6/src/magick.rs#L126
Oh… So it really is the auto orient then! Thanks for your help, I’ll post a GitHub issue later on Lemmy’s repo later(maybe the Ansible one since that’s where the version is defined?) if no one else has done it yet.
Lemmy jank. These kinds of things will be fixed over time! Reddit was real janky when it first started too!