@movq this is brilliant!

Webp, though it has been around for a long while, wasn't fully supported on all browsers until recently. The other formats have been in use for such a long time, proving to work just fine, that the advantages Webp provides haven't been seemingly enough to merit a switch.

Google is also the one behind Webp, and, well, people don't trust, nor like, them much.

@zvava I figure I will know when it is ready, the day I see you using it. Can't wait! :-)

@movq lovely, thanks for sharing! Now you know what I will be using today on a loop.

May I turn your attention to this timeless masterpiece:

https://www.youtube.com/watch?v=zkyFHx4ncR0 (Terra Ferma - Floating)

@zvava looking sweet!

@movq @zvava I think people get sick of everything changing all the time and so don't bother adopting things to change when things are already good enough 🤷

@prologic @movq h.265 is from 13 years ago and support is still incredibly spotty (though it being proprietary probably has a lot to do with that)

also see: jpegxl's adoption (three or six years old depending how you quantify it) which afaik is mostly attributed to google deciding not to put it in chrome (though they changed their stance recently iirc (webp, of course, did not have this problem since it was pushed so hard by google (the browser wars never ended)))

really love this design language i borrowed from firefish/misskey v12, you can even select a bbycll theme in zinnia to make things even more confusing :3 though i myself somehow see past the similarities just knowing how different the codebases are

@prologic Yeah, but isn’t it from 2010? No widespread adoption after 15 years? Is there that much inertia? 🤔 On my box, everything just works – browser, GIMP, ImageMagick, imlib2, … 🤔