Why is it that I can post the attached mp4 but not the source as a gif?
To make the mp4 I encoded the gif in handbrake, which actually made increased the file size but reduced the dimensions.
Source gif: 728*408, 785.5 KiB
Encoded mp4: 640*360, 836.7 KiB
EDIT: For real though, you can always just hotlink embed the source like this (provided the source site allows hotlinking):
Example:

This specific image:

If you’re looking for somewhere to upload files with clear limits which are explained, I suggest catbox.moe
I’m pretty sure that pict-rs doesn’t force-convert things to WebP – the vanilla Lemmy Web UI just fails the upload, and I’m sure that it at least also does PNG and JPEG, as static images go. It might be that your client is doing a conversion to try to work around that limitation?
I only upload photos from the web interface. They all always become webp.
Hmm. I’m certain that they’ve just failed on lemmy.today’s vanilla Lemmy Web UI, not converted.
goes to test
I just created a test (non-animated) gif. Trying to upload it just fails — that is, one can select it and try to upload it, but the Web UI never inserts the uploaded image URL in the textbox.
Here it is on catbox.moe:
If I convert it to a PNG, a format that pict-rs does understand, it uploads without being converted to WebP:
Maybe it’s something unique to lemmy.blahaj.zone?
EDIT: There’s an option in the docker/docker-compose.yml in the lemmy git repo showing an example of how to add an option to force pict-rs to convert everything to WebP. So my bet is that lemmy.blahaj.zone has done that:
https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml
EDIT2: @Ada@lemmy.blahaj.zone would know.
We run our own custom image caching setup. I’ll ask Kaity to look in to it and see what’s going on