Now that #Dolby has launched a #patent lawsuit over #AV1, unless I'm mistaken we're about to have a repeat of the #Unisys #GIF patent situation where all #browser⁠s must remove support for widely-used image and video formats, namely AV1, #AVIF, #WebP, #WebM, #VP8, and #VP9.

This is really bad. The only other widely supported video codec is #MPEG-4 (which is also patented) and the only other widely supported lossy image format is #JPEG (which is rather inefficient).

What do we do?

@yonle

Oh, I'm on #GoToSocial, so I already have 6000 character limit and markdown. Very happy with it.

I haven't tried any of the *oma/*key services, but my only criticism of them is that the web interfaces are kinda heavy for my tastes. Pretty, though.

I just wish Mastodon wouldn't be so strict about the limit. I don't think it's a good policy, although I understand the rationale behind it.

The main thing I do miss about Mastodon is the "reach" (federation-wise), and how well stuff like search works. Things feel a touch more limited on GoToSocial, although it has gotten a ton better in the last couple of years.

I also really wish Mastodon would support #AVIF images. It's a fantastic format with amazing compression for low-quality images (for social sharing, rather than photographic purposes). #GoToSocial added support for the format, but the pictures don't show up at all on the Mastodon interface. :(

Веб-графика, которая вредит: что разработчики делают не так

Обратимся к статистике: по данным с https://httparchive.org/ за последние 6 лет средний размер веб-страницы значительно увеличился. Если в декабре 2019 года средний вес десктопной веб-страницы составлял 1,9 МБ, то сейчас он уже 2,9 МБ для десктопа и 2,6 МБ для мобильных устройств. Это рост на 50% за 6 лет, причём изображения составляют до 40% общего веса страницы. С увеличением разрешения экранов, усложнением дизайна и тенденцией к использованию изображений высокого качества нагрузка на сайты продолжит расти. Это напрямую влияет на скорость загрузки, потребление трафика и, в конечном итоге, на пользовательский опыт. Просматривая недавно пул-реквест, я заметил, что туда добавили новые изображения. Меня удивил выбор формата: для картинок без прозрачности использовали PNG. Это кажется избыточным, так как для многоцветных изображений лучше подходят форматы вроде JPEG, которые весят меньше. Я решил провести эксперимент: оптимизировал и переконвертировал изображения в JPEG, WebP и AVIF, сохранив качество на глаз неотличимым от оригинала.

https://habr.com/ru/companies/alfa/articles/1012848/

#Веб #графика_для_сайта #html #css #react #nodejs #avif #webp

The HTTP Archive

The HTTP Archive tracks how the web is built. We periodically crawl the top sites on the web and record detailed information about fetched resources, used web platform APIs and features, and execution traces of each page.

#Blender 5.1 supports #AVIF but doesn't change the default image quality. JPEG, #WebP, and AVIF are all set to image quality 90.

If you don't change the value, AVIF files are larger than WebP files.

The same visual quality needs different values.

https://www.industrialempathy.com/posts/avif-webp-quality-settings/

AVIF and WebP encoding quality settings

AVIF and WebP are modern image formats that generally produce smaller file sizes compared to the widely used JPEG format. This post explains...

The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl).

JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in.

We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG.

😜🖖🏽

The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl). JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in. We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG. 😜🖖🏽
Convert 100 Images to WebP and AVIF in 10 Seconds

YouTube