A lot is going on in the Bugzilla issue for JPEG XL support… 👀
It really looks like JPEG XL is finally coming to Firefox! 😍
#browser #Firefox #JXL #JPEGXL #JPEG #Web #imageCompression #codec #codecs
A lot is going on in the Bugzilla issue for JPEG XL support… 👀
It really looks like JPEG XL is finally coming to Firefox! 😍
#browser #Firefox #JXL #JPEGXL #JPEG #Web #imageCompression #codec #codecs
Hey @gianni I was just chatting with @yawnbox about a wild range of tech things, and, since I am starting to host an Immich instance in my home, I am considering to convert all my emails to JPEG XL, and I was wondering if there is a way to do so without risking to lose any metadata.
I am happy to read any links you might have but I need them to be as simple as possible because encoding/decoding stuff confuses me a lot. Not my thing… This is why I found your article explaining how AV1 works in simple words absolutely illuminating! Anyway, I just want to save storage space.
Also, I am a big big fan of Aviator, and I have been following your work for a while. Thanks so much for all of it!
#JXL #JPEGXL #JPEG #encoding #decoding #image #metadata #compression
With the speed around #JpegXL picking up (now in #Firefox and #Chrome nightlies), I'm wondering what good use of an #HTML srcset would be there.
As JXL's progressive compression is good, we don't need different files in the srcset (so there's no need to load the first few KiB again when zooming in), but how can or should the HTML somehow tell the browser that for (say) up to 800px width it can request the Range: bytes=0-12345, and the next usable zoom level of 1600px needs the first 42KiB?
I hope the F-Stop Gallery app for Android gets updated with WebP and JPEG XL support.
For now, I switched to Fossify Gallery.