stsquad

Magic Wormhole - it's been around awhile but it's super useful for moving files from your internet connected server to your phone without going through multiple hops copying stuff to you local machine and finding a cable.

That's how it starts. Before you know it you'll be buying no-name smart bulbs from Ali Baba and investigating custom firmware for full local only control.

We are about two thirds of the way in and Disney's terrible colour space handling aside it's a banger of a show. I have vague memories of the original TV adaptation but certainly prefer the modern one.

You can play bedrock on Linux using either the mcpelauncher or setting up waydroid. Both require you to have purchased it via Google play.

Quite. Go to the big services that know how to moderate and maintain (and importantly pay for) a public square. But also encourage the interesting ones enable federation for wider coverage.

There are some advantages to algorithms for discovery - it's certainly is more user friendly. It's just a shame they tend to enshitify or become toxic. Bluesky seem to offer an API of sorts to plug in feeds you create. Perhaps open algorithms are more accountable?

QEMU is always going to focus on emulation fidelity first and there are few shortcuts. With floating point the differences aren't generally in the numbers but in how the NaNs and other edge cases are handled. If you want to execute FP heavy code you should be cross compiling anyway.

QEMU absolutely will use hardware floating point where it can but only when it will give the correct results. FEX and Box64 are user mode emulators which achieve their speed by avoiding emulation where they can buy thunking at API boundaries.

They won't directly support it because in their view the Google Play process is a more secure way of verifying they supplied the binaries than is possible of f-droid. If reproducible builds were possible maybe there could be some mechanism to verify a given binary is built from a given commit of the source tree.

Other way around. Loyalty cards have always been about getting that sweet sweet data about customer habits.

Btrfs never really worked out for me (I think default COW doesn't play nice with VM images) and ext4 works great.

Pretty much. From v8.0 onwards all the extra features are indicated by id flags. Stuff that is relevant to kernel mode will generally be automatically handled by the kernel patching itself on booting up and in user space some libraries will select appropriately accelerated functions when the ISA extensions are probed. There are a bunch off advisory instructions encoded in the hint space that will be effectively NOPs on older hardware but will enhance execution if run on newer hardware.

If you want to play with newer instructions have a look at QEMUs "max" CPU.