Yep, that's the proper way (Since you can specify the metadata correctly)
But there's also an older rather cursed way, a specially crafted colour profile that a compatible viewer would see and then act as if the image data was in a specific HDR format. It worked too, a few viewers support it, but it's a pretty terrible way to handle it so it's been deprecated.
I actually used it as part of a pipeline to turn Xbox HDR screenshots into HDR JXL images, the JXL encoder at the time would recognise it and apply the right metadata itself.
And PNG is so old that it lacks basic modern features like HDR support.
You can actually store HDR images in PNG (Even BMP, but that's cursed), you just need to include the right metadata, and have a client that supports said metadata. Without it, the image looks a bit funky, but still legible.
Now WebP on the other hand, is incapable of storing HDR images. The lossless mode is limited to 8bpc images, and Google killed off WebP2 in favour of AVIF (Which doesn't have a dedicated lossless mode), which could have fixed those limitations.
What they’re saying is that a web server can create a traditional jpeg file from a jpeg xl to send to a client as needed.
Other way around, you can convert a "web safe" JPEG file into a JXL one (and back again), but you can't turn any random JXL file into a JPEG file.
But yeah, something like Lemmy could recompress uploaded JPEG images as JXL on the server, serving them at JXL to updated clients, and converting back to JPEG as needed, saving server storage and bandwidth with no quality loss.
Can you explains the knitpicking? They specifically decided that only objects orbiting our star can be Planets. It wasn’t an oversight but intentional. How can that be explained? Why do that?
Because we're not going to be visiting any exoplanets anytime soon, so it's not like we can actually check how much they've cleared their orbits.
No, MS has been "shipping" curl with Windows for ages, it's just that legacy powershell has an alias for curl to their internal download module that predates the bundling. And they won't change that because it has backwards compatibility risks.
Upside is, it's a literal alias. "curl" uses the internal module while "curl.exe" uses the normal app.
Further upside, if you use the up to date version of powershell, that alias is gone as they removed it during the transition.
That's the point of the feature though. POP3 moves emails, it's really a transfer protocol rather than an access protocol.
I assume Google is killing it since they assume they're effectively in-charge of email outside of things like company Outlook accounts. They've got no need to worry about people migrating to gmail, since everybody starts out on it now.
They're called "selections", the main ones being PRIMARY and CLIPBOARD, and it's effectively a form of IPC mediated by X. When you select something, that goes into the PRIMARY selection, while when you copy something, it goes into both PRIMARY and CLIPBOARD.
The problem is that "middle mouse click" isn't actually paste, it's "insert primary selection". As long as they're in sync you won't notice any issue (Ctrl+V and MMB will both insert the same content), as soon as they're out of sync you're suddenly exposed to an implementation detail of the X11 protocol.
And it's easy to go out of sync, simply copy something and then select unrelated text, now Ctrl+V and MMB will output different things. It can be useful, e.g. if you're having to copy a bunch of different pieces of text from one window to another, you can simply select and MMB, no keyboard needed, but it's not intuitive IMO, and conflicts with modern usage of the middle mouse button (Get it wrong when trying to open a link in a new tab and you'll dump whatever text you last selected into the site instantly)
Also, these selections aren't a thing under Wayland, it's been re-implemented as a normal paste operation there. The question is actually whether the middle mouse button should be treated like any other mouse button or have this special behaviour by default. My vote is to expose it via the mouse settings applet and leave it up to users, like any other special mouse button.
I used to do it back when gmail first started, I connected it to my previous email account so anything addressed to my old account would get transferred to my new one.
I could probably count the number of emails it ever retrieved on one hand.
So is this a matter of people turning mostly-static websites into React monstrosities or is it something else?
Yep, replaced simple HTML with JSON and client side templating, realised it was inherently slower so re-invented server-side generation (now called SSR, server-side rendering, because everything needs a fancy name), and then merge it all together on the client (rehydration).
All this for content that is 99% static and doesn't need that level of interactivity, even the linked site is doing it for some reason, and they don't even have comments or something that would explain it. They're using it purely for navigation where a plain link would suffice.
Rust has no stable inter-module ABI, so everything has to be statically linked together. And because of how "viral" the GPL/LGPL are a single dependency with that license turns the entire project into a GPL licenced one.
So the community mostly picks permissive licenses that don't do that, and that inertia ends up applying to the binaries as well for no real good reason. Especially when there's options like e.g. MPL.
It kinda amazes me that CLAT still isn't universally supported, e.g. Windows is only just getting it now.
Mobile adoption is pretty good on the other hand, a lot of the big providers went v6 only years ago without much issue (e.g. Telstra, my provider, went single stack v6 back in 2020.
I also just checked the sandboxing status directly in Firefox.
And I'm kinda of cheating, I knew they used it since I've got an unsupported configuration with HW video decoding. It's caused by their sandbox blocking certain things, and it's a known issue. Nvidia drivers don't support VA-API, Firefox only supports VA-API. There's an adapter library available, but it doesn't work in Firefox unless you disable the sandbox.
I thought we got it from the Babylonians, turns out we actually got it from the Ancient Egyptians.
Nope, it's just down to how many "decans" you could see at any one point during the night.