Having multiple sufficiently-powered virtual machines makes OS development really low friction. Though I’d personally go for a blade subrack instead.

Ah good. Now I know what specs not to buy.

Sadly Microsoft didn’t specify where on the keyboard the key has to be.

In order to find out, hit the keyboard with your head; wherever your forehead touches the keyboard first is where the key is supposed to be.

Yeah, I deserve that. I’m just gonna leave my typo. Thanks for the laugh!

1024 = 2¹⁰

FYFY

Seeing as they melt the stuff, I’m not sure the grains need to be rounded.

The problem for chipmakers is not the sourcing of materials itself, but the purity of the sourced material. So don’t worry about public beaches disappearing into Intel’s hopper-feeder.

I have one (came with my display) and it works really well. Plus it’s safe for their nanotextured displays (which are sensitive to having their nanotexturing worn off by cloth that’s even mildly abrasive).

The actual video this article was based on

As I’m saying, I don’t think you need to: manually subscribing to each trusted instance via ActivityPub should suffice. The pass/fail determination can be done when querying for known images.

How about a federated system for sharing “known safe” image attestations? That way, the trust list is something managed locally by each participating instance.

Edit: thinking about it some more, a federated image classification system would allow some instances to be more strict than others.

And he immediately got flamed for it (/s)

User engagement is indeed difficult, and I think it works better if users don’t have to scroll through a mountain of text (including the inevitable apology for yet another late update) that doesn’t interest them.

Their blog would work so much better if PINE64 stopped bundling their updates in one big wall-of-text post and would simply publish them as they came in (or were finished, in the case of a more in-depth article).

Such retention times are often probabilistic (ie. some percentage of bits have retained their proper value) and an “up to” value, which is negatively influenced by such things as the storage temperature and background radiation.

In practice, it might be that the only useful retention time is only a small digit number of years.

Not very. If it boots it boots. Although the ACPI implementation may be a little less buggy (plus you can fix it yourself if needed), so if you’re having power management issues it may help.