just went to look up the status of webp images in mastodon
https://github.com/mastodon/mastodon/pull/11589
turns out support was removed two years ago
@KayFaraday I wish someone did that to Firefox for me 😋
I know I can disable it with about:config var, but I know the code is still there.
@m0xee why would you disable it
@KayFaraday I unconditionally hate everything Google that's my thing 😅
I wish WebP would just cease to exist, together with WebM, VP9, http/2, http/3, etc.
You won't believe the lengths I went to get rid of WebP on my Void boxes, I have half the templates for imaging-related software patched and build the packages myself. It's not that easy with Firefox as it doesn't use libwebp and has its own implementation.
@m0xee it's a good codec though
@KayFaraday I admit, It does have superior compression, but not a game changer, I think it's 10% better on average. I mean I get why Google is interested in it, for them 10% is a lot if they save on that bandwidth, but for everyone else it's not that obvious.
And it hinders the development of new browsers — if it's not based on already existing engines, because once it's universally excepted you have to support it — one more thing to implement 🤷
@m0xee try comparing the size of the original image of this https://imgur.io/a/qUjz3FW in webp vs png
@KayFaraday
"Oops! We couldn't find that page"
Broken link?
@m0xee huh it works for me
@KayFaraday
> there always are corner cases
For example, I've seen with my own eyes several YouTube videos, where VP9 (YT format 248) stream's size was bigger than h264 (YT format 137), but it doesn't mean that h264 is better, in fact it's the opposite, VP9 is better on average.
But only marginally so. So I still hate it 😅