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?
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
https://slrpnk.net/api/v3/image_proxy?url=https%3A%2F%2Fi.pinimg.com%2Foriginals%2F36%2F58%2F2e%2F36582e9915de4e1ece7ec4021b21b268.jpg
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.