ferret

what is that

I hope they are comfortable at least…

This was posted to his low-effort second channel, he is probably leaving it up explicitly because people are using it to discuss ebay bootlegs in the comments.

Nope, lol. These suckers are fucking ancient. There isn’t any processing, you can’t overload something that isn’t actually reading the data or using a protocol.

Is your time & date set correctly?

… your nas only had 12gb of storage??

Magnetic recording materials have historically been metal oxides, I have no clue if that remains true for modern hard drive platters. I guess you could argue that SSDs are stationary sand, but you could make the same argumant for the majority of semiconductors so I don’t think it sufficiently specifies SSDs.

That is 60Hz (or 50Hz), a much lower frequency, by multiple orders of magnitude

Yellow… 🤤🤤🤤

But, my dearest Drag, you miss the point! There will be generations of humans that have no experience of spinning rust, of whirring platters, or of the dreaded tick- tick- tick- of a crashed head and lost data. What will they do?

Breadius

Raise beautiful children together 🥰🥰🥰

Intel really ought to just pull an AMD and spin off their foundry biz

Even with an admin as renewable-hostile as the current one, you just can’t beat cheap, I guess.

The commitment to the bit is admirable.

A modern TV is a really bad example. Most modern gaming computer monitors have grey-to-grey pixel response times measured in nanoseconds. I would not be surprised if that exceeds the fade-time of CRT phosphors.

Six years ago it wasn’t backed up by the highest office in the country

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…

The impact frames are great, animator should be proud.

It is a CPU vulnerability, so while the researchers used QEMU for their example, it is not necessarily specific to it.