this post was submitted on 22 Sep 2025
422 points (98.2% liked)

196

18553 readers
196 users here now

Be sure to follow the rule before you head out.


Rule: You must post before you leave.



Other rules

Behavior rules:

Posting rules:

NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.

If you have any questions, feel free to contact us on our matrix channel or email.

Other 196's:

founded 2 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] lemming741@lemmy.world 126 points 1 month ago (2 children)
[–] stabby_cicada@slrpnk.net 41 points 1 month ago* (last edited 1 month ago) (3 children)

The fact that Kissinger outlived Bourdain proves there is no God.

Though I almost wish Kissinger had lived long enough to see Trump piss away the American power and influence Kissinger sold his soul for. Kissinger should have lay on his deathbed knowing his successors squandered every advantage he won for America, that he steeped his hands in blood and made himself the greatest war criminal in history for nothing.

[–] Soup@lemmy.world 8 points 1 month ago

For people like that I can’t even imagine that they don’t do it for the love of the game. Things always go better for everyone when we work together(should still tell nazis to sit on a stick and rotate, though), people in positions of power like that are cruel for cruelty’s sake. All he did was create more enemies for his country and chased more hate like the lady who swallowed a fly. It never got better because all he did was inject poison into the world and didn’t use any of the US’s influence or power to actually help anyone.

Just a huge piece of shit all around.

[–] subiprime@lemmy.blahaj.zone 6 points 1 month ago

tom lehrer outlived kissinger at least!

[–] Djehngo@lemmy.world 8 points 1 month ago

More compelling than the edit, thank you for posting this.

https://www.bbc.co.uk/news/world-asia-67582813

^ an article describing some of the reason Kissinger was such a vile person, including how he shares some of the responsibility for the rise of the Khmer Rouge

[–] aBundleOfFerrets@sh.itjust.works 61 points 1 month ago (1 children)

Google has apparently been mogged into rewriting the jpegxl reference library in rust to make it more “secure” so that it can be used in browsers (apparently the reason they refuse to put it in chrome, and the reason firefox devs cite) (never mind the fact that this apparently didn’t stop Apple) we can only hope they actually finish the damn thing…

[–] socsa@piefed.social 8 points 1 month ago

To be fair, this isn't just happening out of the blue. Apple had a bunch of zero day, no click vulnerabilities from its media decoders, which were some of the original Pegasus vectors. Complex media rendering is a very legitimate security concern, particularly in the browser space on general purpose machines. IDK if doing a full RUST implementation is the right answer, but the idea of not wanting to add a massive potential attack vector for redundant functionality is not completely insane.

[–] daggermoon@lemmy.world 49 points 1 month ago (3 children)

I uploaded a meme in .jxl and everyone downvoted it because they couldn't see it. If you use a firefox fork please enable it ffs.

[–] SaharaMaleikuhm@feddit.org 15 points 1 month ago (2 children)

Is it not enabled by default in firefox?

[–] daggermoon@lemmy.world 8 points 1 month ago

Nope, Mozilla doesn't trust it to be secure. A newer Rust decoder for Firefox is in development.

[–] ILikeBoobies@lemmy.ca 2 points 1 month ago

Firefox only packaged it in nightly builds.

Stable has the setting but it does nothing.

[–] Jumuta@sh.itjust.works 7 points 1 month ago (1 children)

can you even enable it as an option? I thought they removed it because of "attack surface" concerns

[–] daggermoon@lemmy.world 6 points 1 month ago (2 children)

In can be enabled in about:config but only in nightly. It works in most forks as well. A Rust decoder for .jxl is in development. Mozilla said they will include it in Firefox when finished

[–] rapchee@lemmy.world 3 points 1 month ago* (last edited 1 month ago) (2 children)

~~i just enabled it in firefox stable, 143.0, linux ~~
edit: i have been bamboozled, it does nothing
test your browser for jxl support: https://jpegxl.info/resources/jpeg-xl-test-page

[–] daggermoon@lemmy.world 1 points 1 month ago

Did it actually work?

load more comments (1 replies)
[–] Jumuta@sh.itjust.works 1 points 1 month ago

ah yeah, is that rust implementation the one being written by the chromium jxl team?

[–] ryper@lemmy.ca 6 points 1 month ago

The setting is image.jxl.enabled for those who want to try it.

[–] agentshags@sh.itjust.works 40 points 1 month ago
[–] arsCynic@beehaw.org 29 points 1 month ago* (last edited 1 month ago) (4 children)

For f*&% sake, I'm using JPEG XL on my website for some high res images that are amazingly well compressed using it, and especially to reduce the repository size on Codeberg. Only now discovered that only my niche main browser, Zen, renders them. What a stupid decision; their compression of high quality images is superior. Perfect to use alongside AVIF which does better in low quality images and illustrations and the like, or PNG which is best at preserving images containing text such as screenshots.

[–] ILikeBoobies@lemmy.ca 2 points 1 month ago

Safari renders them.

Firefox forks usually render them because Firefox supports it but Mozilla takes it out of packaged builds.

load more comments (3 replies)
[–] LiveLM@lemmy.zip 22 points 1 month ago

Current Android news have me wanting to beat Google to death

[–] Stern@lemmy.world 20 points 1 month ago
[–] kopasz7@sh.itjust.works 19 points 1 month ago (4 children)

This might be an unpopular opinion, but webp fulfills the same use cases and some more. But it's not jpeg and some SW still doesn't support it.

[–] craftrabbit@lemmy.zip 45 points 1 month ago (1 children)

Except webp has worse compression, doesn't support HDR and has a max colour depth of 8bpc. What makes JPEG-XL great is that it covers loads of use cases and is very future proof.

[–] kopasz7@sh.itjust.works 8 points 1 month ago (2 children)

Webp, on the other hand is "current-proof". JXL's biggest issue is getting adoption, not the technical aspects.

The meme is right, chrome/ium support would do a lot to help adoption. But not even the mainline FF version has support (AFAIK).

[–] edinbruh@feddit.it 10 points 1 month ago

Webp is "current-useless" on account of being unsupported by a lot of software, including Google's own office suite. Just the same as jxl.

At the end of the day, any standard or protocol that is not widely supported is de-facto useless. Some examples are: ipv4 multicast, TCP multipath, MIR, hashcash; all of this are technically valid, but nothing supports them, so it doesn't matter

load more comments (1 replies)
[–] daggermoon@lemmy.world 43 points 1 month ago (1 children)

Except .jxl is backwards compatible with .jpg. You can losslessly convert a .jpg to a smaller .jxl file. Also .jxl is future proof and supports ridiculously high resolutions up to 1 terapixel.

[–] kopasz7@sh.itjust.works 9 points 1 month ago (2 children)

JXL is better on paper/technical specs, but adoption is terrible while wepb is already here as it replaced gifs and most web images.

I have nothing specific against JXL, it's a good format, but I don't feel its necessary either.

[–] craftrabbit@lemmy.zip 10 points 1 month ago

Yeah, I guess if we're being pragmatic/reasonable, you are right. I think jxl use and general adoption would be much more of a symbolic win than a technical one. The problem is that a new image format only reaches general adoption if Google supports it. Webp is a decent Google-developed standard that has reached general adoption because Google pushed and supported it and if Google doesn't support jxl, then you can't use it on the general internet.

This is not about jxl being the better standard, this is about the better standard being non-viable because Google doesn't want it to be.

The caveat here is that jxl is not half as old as webp and this situation might change drastically in a matter of months (I bet ff would be quick to adopt jxl if Google did...) ((although the jxl standard is technically 3 years older than the webp standard))

[–] railwhale@lemmy.nz 6 points 1 month ago

Webp adoption also used to terrible, but now it's mostly fine.

[–] kibiz0r@midwest.social 29 points 1 month ago (1 children)

Kinda missing the point here.

One company shouldn’t be able to pick winners and losers for file formats or protocols.

Google has done it over and over again: https://en.wikipedia.org/wiki/QUIC

Pretty sweet gig, being able to give yourself an 8-year head-start.

[–] kopasz7@sh.itjust.works 9 points 1 month ago (1 children)

They released the gQUIC reference implementation under the BSD-3 licence. What would have been your preferred way?

Google is a monopoly, consequently most of their in-house tech will make waves if they decide to use it.

Or are you suggesting a nefarious purpose, like MS's EEE?

[–] kibiz0r@midwest.social 4 points 1 month ago (1 children)

There’s not really a better way when you’re a monopoly. That’s the problem.

With QUIC and with webp, there was no period of time where the new protocol/format had to compete against other experimental options to see which would win out.

Because Google put it out, and they control an overwhelming share of clients and servers, they were both a foregone conclusion. Google released it, so now it’s a standard. Other companies can either adopt it or fall behind.

This allows them to stack the deck in favor of their portfolio, even if other options were technically superior.

[–] socsa@piefed.social 3 points 1 month ago

I mean the alternative is what Microsoft does with xml documents where they participate in the standards committee, release a reference implementation, and then intentionally break it in Office so idiots whine about open tools "not rendering correctly"

[–] ameancow@lemmy.world 10 points 1 month ago

Fuck webp and the horses it rode in on.

Or I should say, the several supported horses it rode in on, and the rest of the horses standing there looking confused like they have no idea what a webp is even though they can make a preview thumbnail of the webp image, but just can't do anything else with it.

webp feels like a cancer

[–] Psythik@lemmy.world 4 points 1 month ago (2 children)

Why is this topic so hot right now? What did I miss?

[–] themagzuz@lemmy.blahaj.zone 6 points 1 month ago

i just saw a post hating on webp on my timeline, and happened to have recently talked with a friend about image formats, wherein this image was made. so i just kinda thought it would be relevant to post

[–] ILikeBoobies@lemmy.ca 1 points 1 month ago

It’s been hot since webp was introduced.

Jxl is just the best image format at present.

[–] pewgar_seemsimandroid@lemmy.blahaj.zone 3 points 1 month ago (1 children)
[–] drkt@scribe.disroot.org 28 points 1 month ago (1 children)

JXL is better at what PNG does than PNG is

[–] pewgar_seemsimandroid@lemmy.blahaj.zone 5 points 1 month ago (1 children)
[–] yistdaj@pawb.social 1 points 1 month ago* (last edited 1 month ago) (1 children)

JPEG XL is partially based on FLIF/FUIF, which boasted/claimed the best lossless image compression on the planet.

[–] pewgar_seemsimandroid@lemmy.blahaj.zone 1 points 1 month ago (1 children)
[–] yistdaj@pawb.social 1 points 1 month ago (1 children)

PNG only supports 4 colour channels, RGBA. JPEG XL supports up to 4099... In case you ever needed that for depth or thermal data or something.

PNG only supports 8 and 16 bits for each colour channel, JPEG XL supports up to 32 bits for each colour channel. In case you have something physically capable of displaying the difference.

I'd talk about HDR support, but PNG added that recently when it also made animation support official, rather than an extension. Which JPEG XL also supports.

To be fair, I still use PNG out of habit, and because I can't show anybody .jxl files over the internet like I can .png files. Also I mentally associate PNG with quality, while JPEG XL sounds like a big JPEG, which it can also be if you switch it to lossy mode.

png is still better.

[–] lost_faith@lemmy.ca 2 points 1 month ago

Question: Why do I always have issues opening the memes from here? I use ff+ubo and yours is the only instance I need to use chrome or edge to see the full sized image

load more comments
view more: next ›