@[email protected] I tried uploading this 35 second loop to Fedia as a 5.7MB webm video before I uploaded this 5.7MB bitcrushed gif instead. It seems Mbin throws 500 Server Errors whenever it receives a webm upload. That’s too bad. The webm looks a lot better, and this post actually links to the webm version on Catbox. I think that’s how this post worked, too.
I only rarely host media on my instance itself. Catbox lets me control exactly what the file is, as the file is not subjected to any post-upload conversions.
But many instances will actually grab a copy of the image and cache thumbnails at various resolutions.
Thunder’s current version actually attempts to load the instance cached versions of images, though this has unintentionally left it unable to load and display the source file.
In the future, the plan is to make this configurable, to allow users to set an image size they’d like Thunder to request from the instance cache instead of loading full images every time, allowing for faster browsing and conserved bandwidth.
Sorry for missing this, seems mention notifications aren’t working for me at the moment (hyphens have always been problems but because /kbin allowed them we’re stuck with them, even though almost all AP platforms like mastodon and lemmy don’t allow them) (we had fixed it four months ago but… I guess something happened since then). Not sure I know much about media uploads but can at least look into it / talk to one of the other team members that usually knows a lot about this stuff.
@[email protected] I tried uploading this 35 second loop to Fedia as a 5.7MB webm video before I uploaded this 5.7MB bitcrushed gif instead. It seems Mbin throws 500 Server Errors whenever it receives a webm upload. That’s too bad. The webm looks a lot better, and this post actually links to the webm version on Catbox. I think that’s how this post worked, too.
I only rarely host media on my instance itself. Catbox lets me control exactly what the file is, as the file is not subjected to any post-upload conversions.
But many instances will actually grab a copy of the image and cache thumbnails at various resolutions.
Thunder’s current version actually attempts to load the instance cached versions of images, though this has unintentionally left it unable to load and display the source file.
In the future, the plan is to make this configurable, to allow users to set an image size they’d like Thunder to request from the instance cache instead of loading full images every time, allowing for faster browsing and conserved bandwidth.
Sorry for missing this, seems mention notifications aren’t working for me at the moment (hyphens have always been problems but because /kbin allowed them we’re stuck with them, even though almost all AP platforms like mastodon and lemmy don’t allow them) (we had fixed it four months ago but… I guess something happened since then). Not sure I know much about media uploads but can at least look into it / talk to one of the other team members that usually knows a lot about this stuff.