dont-accept-webp VS pik

Here's the one for firefox: https://github.com/jscher2000/dont-accept-webp

25. Don't Accept image/webp 0.8.2 Strip image/webp from Accept: headers, which should discourage servers from replacing JPEG and PNG images with WebP images. https://github.com/jscher2000/dont-accept-webp

Add-ons can intercept requests and modify Accept headers globally (example) or based on parameters added to the URL (example) but I don't know how easily they can define new script methods that you could use in a page, if that is a requirement, or determine that it is the first GET request in a tab, if that is a requirement.

If you're on Firefox there's a tiny add-on that has helped me a lot with this issue: https://github.com/jscher2000/dont-accept-webp

Same here, https://github.com/jscher2000/dont-accept-webp

You do know that Google was one of the main contributors to JPEG XL (see https://github.com/google/pik )

Google was a big part of JPEG XL and is actively working on libjxl as well... and JPEG XL is also based on FLIF and google's pik: https://github.com/google/pik so pretty weird.

legally they had no choice because jpeg xl is based on flif.info and https://github.com/google/pik but the flif has LGPL license which should open source the rest.. however regardless the media group didn't really do much other than write some standard and slap their name on it. Wasn't their work.

https://github.com/google/pik went into jxl, webp is based on their video codecs

The specific variant of ANS coding that is used in JPEG XL is basically the same as what was used in pik: https://github.com/google/pik/blob/2fb44c4834348392d0401ad9bab7cd314d85241e/ans_encode.h

Image compression researchers at Google designed the image format PIK