|
username
|
2026-03-07 10:41:56
|
my message was just based on how the website behaves
|
|
|
Cy
|
2026-03-07 10:42:08
|
yeah, the compression step is done on the client side for some reason
|
|
2026-03-07 10:42:43
|
https://pdsls.dev/at://did:plc:mceibkdhjwzqecdxraou3wwn/app.bsky.feed.post/3mgnrciug2s2y
|
|
|
username
|
|
Cy
https://pdsls.dev/at://did:plc:mceibkdhjwzqecdxraou3wwn/app.bsky.feed.post/3mgnrciug2s2y
|
|
2026-03-07 10:48:50
|
If I use [gallery-dl](https://github.com/mikf/gallery-dl/) on https://bsky.app/profile/did:plc:mceibkdhjwzqecdxraou3wwn/post/3mgiu5dchfo2u then it does get the JXL file along with saving it properly as a ".jxl"
|
|
|
Cy
|
|
username
their system is as follows (more or less):
1. decode user uploaded image/file to pixels.
2. encode pixels to quality "100" 4:4:4 YUV JPEG restricted to a max res of 2000x2000.
3. these JPEGs then get sent through [imgproxy](https://imgproxy.net/) at what seems like almost completely default settings (medium quality non-progressive JPEG) for display on the website.
|
|
2026-03-07 11:21:43
|
yeah, those first 2 steps are entirely client side ([source](https://github.com/bluesky-social/social-app/issues/5855#issuecomment-2501483737))
|
|
|
Kampidh
|
2026-03-08 09:25:44
|
oh sweet, they finally updated it? last time I tested it the jxl still wont load (around 2 months ago)
|
|
|
Cy
|
|
Kampidh
oh sweet, they finally updated it? last time I tested it the jxl still wont load (around 2 months ago)
|
|
2026-03-09 02:02:59
|
~~I think that was because imgproxy didn't support jxl files at the time (~2 months ago), but I don't know all the details.~~
It's possible that it didn't work because the client wasn't able to decode the jxl image (it reconverts all images to jpegs)
|
|
|
jonnyawsom3
|
2026-03-09 03:27:40
|
Imgproxy got support a year ago, I know because it was me, Kampid and the libvips maintainer who discussed it on Bsky when we first tried it
|
|
|
Cy
|
2026-03-09 03:53:54
|
*I stand corrected*
|
|
|
jonnyawsom3
|
2026-03-09 04:03:56
|
https://bsky.app/profile/jonnyawsom3.bsky.social/post/3lawolkgpk22x
|
|
|
Prower
|
2026-03-14 03:14:46
|
DXO recently released Pure Raw 6 with their new High Fidelity DNG export option. This applies some kind of lossy compression to the DNG that appears to be very good. I know the DNG 1.7 spec has support for JXL compression but I can't find anywhere that confirms this is what they are using. They claim it is proprietary AI magic but I have a hunch it's just JXL, would be pretty neat to confirm that though. https://www.dxo.com/dxo-pureraw/#whats-new
|
|
|
Mine18
|
2026-03-14 04:49:26
|
<@794205442175402004> random question but how many clients report the lowest amount of support? (no avif, no jxl, maybe even no webp)
|
|
|
o7William
|
2026-03-14 05:55:57
|
MS Paint <:kekw:808717074305122316>
|
|
|
_wb_
|
|
Mine18
<@794205442175402004> random question but how many clients report the lowest amount of support? (no avif, no jxl, maybe even no webp)
|
|
2026-03-14 07:01:46
|
Quite a lot actually, images downloaded via Javascript or by apps usually don't send any image format support in their request header.
|
|
|
Mine18
|
2026-03-14 07:02:28
|
so they automatically download the jpeg versions? how about device clients?
|
|
|
|
cioute
|
2026-03-18 08:15:16
|
what about fork of [jpegview](https://github.com/sylikc/jpegview) with jpegli (better jpeg codec) and option of jpeg-xl as extraction format?
|
|
|
monad
|
2026-03-19 11:15:51
|
jxl@home when
https://github.com/illixion/distributed-jxl-converter
|
|
|
Mine18
|
|
monad
jxl@home when
https://github.com/illixion/distributed-jxl-converter
|
|
2026-03-20 03:06:56
|
if every website would convert their jpegs to jxl with this, I would probably help
|
|
|
|
veluca
|
2026-03-20 03:47:29
|
of all the things...
|
|
|
HCrikki
|
2026-03-20 08:47:51
|
seems all chrome stable installs are now on 146, with jxl built and activable either by users themselves or in an origin trial
|
|
|
AccessViolation_
|
|
veluca
of all the things...
|
|
2026-03-20 08:57:53
|
it gets sillier yet, there are people reverse engineering minecraft world seeds like this
|
|
|
Kleis Auke
|
|
Kleis Auke
This has now been deployed. For example:
https://wsrv.nl/?url=https://github.com/libjxl/conformance/raw/master/testcases/animation_icos4d/input.jxl&n=-1&output=webp
However, some custom bitdepth images are currently broken due to the issue described in PR <https://github.com/libvips/libvips/pull/4830> (e.g. <https://wsrv.nl/?url=https://github.com/libjxl/conformance/raw/master/testcases/sunset_logo/input.jxl&output=png>).
|
|
2026-03-21 11:56:15
|
FWIW, the issue with custom bitdepth images should be fixed now (thanks to libvips 8.18.1).
|
|
|
whatsurname
|
|
HCrikki
seems all chrome stable installs are now on 146, with jxl built and activable either by users themselves or in an origin trial
|
|
2026-03-21 01:33:02
|
It's infeasible to run an origin trial on 146, I don't know where you get it
|
|
|
Aerocatia
|
2026-03-23 02:26:17
|
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/149
JPEG XL is in 149 not nightly?
|
|
|
Meow
|
2026-03-23 02:38:12
|
> **JPEG XL image support: Rust-based decoder**: `image.jxl.enabled`
>
> The previous C++ JPEG XL image decoder has been replaced with a new Rust-based implementation that uses the jxl-rs library. (Firefox bug 1986393).
|
|
2026-03-23 02:40:06
|
and v149 is scheduled to be a release tomorrow
|
|
|
whatsurname
|
2026-03-23 03:22:31
|
No, it's still nightly only.
They fixed https://bugzilla.mozilla.org/show_bug.cgi?id=1922974 though, so release builds won't have that nonfunctional preference.
|
|
|
lonjil
|
2026-03-23 03:39:25
|
The notes above are for the beta channel though.
|
|
|
whatsurname
|
2026-03-23 03:40:37
|
Yes and it's incorrect
|
|
|
Quackdoc
|
2026-03-23 03:48:51
|
Mozilla moment
|
|
|
whatsurname
|
2026-03-23 05:09:51
|
You can subscribe to https://bugzilla.mozilla.org/show_bug.cgi?id=2016688 for when it will be built on beta/release builds
|
|
|
VcSaJen
|
|
whatsurname
Yes and it's incorrect
|
|
2026-03-23 06:41:05
|
Not the first time they make that mistake for JXL.
|
|
|
Demiurge
|
2026-03-24 03:37:14
|
So it's already in stable chrome. And stable safari. But not firefox?
|
|
2026-03-24 03:37:19
|
Wow.
|
|
2026-03-24 03:37:33
|
Not what anyone expected at all I don't think
|
|
2026-03-24 03:37:52
|
Mozilla ain't what it used to be
|
|
|
Quackdoc
|
2026-03-24 03:49:54
|
what?
|
|
2026-03-24 03:50:00
|
I think most people expected it lmao
|
|
|
whatsurname
|
2026-03-24 05:08:06
|
It's behind a flag on stable Chrome
Not many users will enable it, Firefox can still catch up
|
|
|
HCrikki
|
2026-03-24 06:51:41
|
by design. even the very best possible promotion would struggle getting 100k users to manually enable. only origin trial or being on by default on at least one release channel like Dev that will give it enough users
|
|
|
A homosapien
|
2026-03-24 07:06:37
|
A battle for second place for JXL adoption
|
|
|
|
Squid Baron
|
2026-03-24 09:02:45
|
we should start scamming people, enable the JXL flag and we will send you bitcoin
|
|
|
Demiurge
|
2026-03-25 01:58:52
|
Ha
|
|
2026-03-25 01:59:31
|
Didn't realize it's still behind a flag and not enabled by default
|
|
2026-03-25 02:00:25
|
But I guess it makes sense while jxl-rs is getting some last minute refinement
|
|
|
Meow
|
2026-03-25 06:54:49
|
Is the implementation on Safari considered outdated now?
|
|
|
|
veluca
|
2026-03-25 07:35:26
|
"last minute" is a bit of a strong word
|
|
|
_wb_
|
|
Meow
Is the implementation on Safari considered outdated now?
|
|
2026-03-25 07:36:24
|
I wouldn't say outdated, but the integration in Safari was never complete (no animation, no progressive).
|
|
|
Meow
|
2026-03-26 10:13:46
|
I can't recall if WebKit would use jxl-rs
|
|
|
username
|
|
Meow
I can't recall if WebKit would use jxl-rs
|
|
2026-03-26 10:14:06
|
it's libjxl
|
|
|
Meow
|
2026-03-26 10:14:15
|
Yeah it's now
|
|
2026-03-26 10:15:35
|
For me it's like that Apple implemented JXL and that's all
|
|
|
VcSaJen
|
2026-03-26 12:04:34
|
On Mac/iOS webkit does not use any bundled libraries, it just calls OS. OS does not need to swap to decoder-only implementation when encoding is also needed.
|
|
|
_wb_
|
2026-03-30 05:45:44
|
https://github.com/WordPress/gutenberg/issues/76756 does someone feel like commenting that jxl support would also be nice to add while they're at it?
|
|
|
Kleis Auke
|
2026-03-30 06:34:11
|
It was removed with PR https://github.com/WordPress/gutenberg/pull/76639.
|
|
2026-03-30 06:35:34
|
I think it needs to be added to WordPress Core first.
|
|
|
HCrikki
|
2026-03-31 08:08:54
|
not quite jxl-specific, but DNG is now an ISO standard, which may reduce the proliferation of proprietary raw formats with inefficient uncompressed or oldjpeg compression
|
|
|
jonnyawsom3
|
2026-03-31 08:17:44
|
Now if only they made better use of JXL's capabilites instead of just replacing the old JPEG with it...
|
|
|
spider-mario
|
2026-03-31 09:55:38
|
I have some doubts that Canon or Nikon will jump to replace their raw formats with DNG
|
|
2026-03-31 09:55:47
|
but I would be happy to be proven wrong
|
|
2026-03-31 09:55:53
|
(especially by Canon)
|
|
|
HCrikki
|
2026-03-31 10:12:02
|
photographers have been complaining about raw filesize since forever. dng 1.7 with jxl would be a no-brainer since other formats are behind by now
|
|
2026-03-31 10:13:49
|
its possible theyd be extended with newer codecs or a jxl payload, but imo standardizing on a single industry format would simplify workflow and limit loss of metadata and visual quality across conversions and edits
|
|
|
RaveSteel
|
2026-03-31 10:39:36
|
Manufacturers willl probably keep peddling their own proprietary formats
|
|
|
jonnyawsom3
|
2026-04-01 07:02:55
|
Not to mention, if they did it 'right' (no weird tile sizes, using kCFA instead of a greyscale mosaic, tuned encode settings), it would almost certainly be smaller than Adobe's DNG output too
|
|
|
RaveSteel
|
2026-04-01 07:43:18
|
I don't have losslessly compressed raw files, but someone who has could compare using adobe's dng conmverter software
|
|
|
jonnyawsom3
|
2026-04-01 08:14:59
|
Just wish the Adobe CLI tool wasn't such a nightmare to use
|
|
|
RaveSteel
|
2026-04-01 08:53:50
|
have you read the documentation? it's pretty bad as well
|
|
|
jonnyawsom3
|
2026-04-01 09:18:56
|
Of course, otherwise I never could've got it working
|
|