The_Decryptor

SpaceX wrote in its July permit application — under the header Specific Testing Requirements — Table 2 for Outfall: 001 — that its mercury concentration at one outfall location was 113 micrograms per liter. Water quality criteria in the state calls for levels no higher than 2.1 micrograms per liter for acute aquatic toxicity and much lower levels for human health

Cool, you can drink the mercury water, but I’ll pass thanks.

I’ve got some numbers, took longer than I’d have liked because of ISP issues. Each period is about a day, give or take.

With the default TTL, my unbound server saw 54,087 total requests, 17,022 got a cache hit, 37,065 a cache miss. So a 31.5% cache hit rate.

With clamping it saw 56,258 requests, 30,761 were hits, 25,497 misses. A 54.7% cache hit rate.

And the important thing, and the most “unscientific”, I didn’t encounter any issues with stale DNS results. In that everything still seemed to work and I didn’t get random error pages while browsing or such.

I’m kinda surprised the total query counts were so close, I would have assumed a longer TTL would also cause clients to cache results for longer, making less requests (Though e.g. Firefox actually caps TTL to 600 seconds or so). My working idea is that for things like e.g. YouTube video, instead of using static hostnames and rotating out IPs, they’re doing the opposite and keeping the addresses fixed but changing the domain names, effectively cache-busting DNS.

SpaceX like to dump their waste in the closest river.

Set that minimum TTL to something between 40 minutes (2400 seconds) and 1 hour; this is a perfectly reasonable range.

Sounds good, let’s give that a try and see what breaks.

I like the idea that it’s hard to boil water, but easy to find a person whose body temperature is exactly the same as the reference point.

She was pushing for Trump to have it since it was first announced she won it. It’s got nothing to do with her wanting to protect her country or whatever, she’s got a terminal case of Trump brainworms.

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.

I’ve seen zero RISC devices in the wild

Ever seen an Nvidia GPU? They’ve been using them for years. One estimate is they shipped 1 billion cores in 2024.

Not as end user programmable chips of course, but the “end user devices” market is only a small part of the total industry.

He founded Bluesky, but after helping Elon buy Twitter, he left.

Ehh, I’d pass on Ladybird. I’ve been donating to Servo myself.

Microsoft did.

I just checked my phone, it was on by default for me.

Well no you can translate, but it just seems that nobody has actually made a product to do so.

e.g. those M.2 SSD to USB adapters, those aren’t speaking NVMe to the host device. They either talk the traditional USB “bulk transfer” protocol, or potentially SCSI, translating that to NVMe for the SSD itself.

Man, it sure would be helpful for my argument if I could.

I went back and checked the ones I was looking at, very helpful fine print stating “not for NVEM ssds”, so they all only work with mSATA M.2 SSDs, hell of a let down.

Especially since you can get M.2 to SATA adapters, so people stuck with SATA only motherboards can still upgrade their storage.

Literally the same deal when companies stopped making IDE drives, people just used SATA to IDE adapters instead.

Git itself (Or any other VCS for that matter) really should treat symlinks as special, similar as to how btrfs stores everything as “reflinks” internally. They be stored as special references to other tracked objects (so it’d be impossible to commit a symlink that pointed at anything other than a checked-in file, and ensure they always match), and git can materialise them as needed.

eg I have a photo of my foot when I broke it off at the ankle.

How on earth did you manage that?

Same reason we still haven’t banned smoking or gambling, once you’re an adult you’re on your own.

Unless it’s drugs of course, can’t have them.