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

weekend = day_of_week in (“sat”, “sun”)

As a bonus this completely sidesteps the issue of what day is 0 or 1.

If there’s water between the membranes an alternative is to wait a long time for it to dry out (months).

Yeah, hobbit-serial architectures lack performance.

So the Fellowship of the Ring was made up of an elf, a dwarf, two humans, a maia and one hobnibble?

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).

Interesting. I have the classic FSSK on order. How’s the keyfeel compared to, say, a model M?

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)

Nowadays macOS maximises like Windows does. Whether that’s “doing it right” is something else entirely.

Mac OS (…) was okay, but reliant on the global menu and weird drop-downs.

See Fitt’s law for why the Mac’s menu bar is the way it is.

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).

I’m sure your colleagues will want one too when they see you using one :)