Here we are with a community celebrating art, some of us might like to archive it. But no, inevitably it’s google ‘owned’ transcoded, WebP. I have an extension to re-encode back to an old format, but that’s lossy-lossy transcoding, not good. I suspect it’s a Lemmy thing, but what would it take to get non-lossy here?
Don’t upload directly through Lemmy if you’re looking to preserve the original quality. That is controlled by your instance admin if you wish to have them change it message them.
Most people including myself uses a service like https://catbox.moe/
Hmm, shall look into it.
So, when I open an image in a new tab I get
Type: WEBP (document.contentType=image/webp)
Dimensions: 557px × 900px
Seems like it was a jpg, but now it’s webp (and yes I’ve tried to convince firefox to not like webp, seems to be ignored.
Is there a switch the admin can pull to stop this? They’re pretty nice, but I’d like to make it easy on them.
Oh interesting, this is a bit different than what I thought you were experiencing.
So when I visit that post from my instance that doesn’t happen. https://ani.social/post/4400463
It appears slrpnk.net is using a new feature called Image Proxying Its meant to protect you from data-mining and optimizes the data used.
I’m not aware of it theres a way to shut it off per user or not. I would recommend asking slrpnk.net’s admin.
Mffh cool, and annoying in this case, but generally good. Might just stick with it and use another instance as needed. Thank you kindly for letting me know.
Usually if I expand a thumbnail in my feed it will be webp but if I click and open that image in a new tab it will be GIF, JPEG, PNG, BMP, etc
So, when I open an image in a new tab I get
Type: WEBP (document.contentType=image/webp)
Dimensions: 557px × 900px
Seems like it was a jpg, but now it’s webp (and yes I’ve tried to convince firefox to not like webp, seems to be ignored.
Is there a switch the admin can pull to stop this? They’re pretty nice, but I’d like to make it easy on them.
