AllNewTypeFace

They elected a right-of-centre minority government which depends on the local neo-Nazi party (the “Sweden Democrats”) for votes and so panders to them. They’re halfway into their term, and polling suggests that it’ll be a 1-term government, with a left-of-centre coalition almost certainly taking over in 2026.

Could have been worse. He could have been from a culture in which saving someone’s life means that you become responsible for them for the rest of their life. Then you’d have had to rig up some kind of situation in which he saves your life so you become even.

That looks like an Iain Banks non-sci-fi book jacket

So, like the screen in the PlayDate?

Both of these services appear to be dependent on BlueSky. I.e., if BlueSky ceased existing, or cut them off from its API, they’d die. In that way, they’re not that different from “Log in with Facebook” or similar.

One could theoretically make one’s own independent AT Protocol network, but not in a way that interoperates with BlueSky as a peer. You’re either a subsidiary part of its network or you don’t exist as far as it’s concerned, which is a much poorer value proposition than ActivityPub and related protocols.

No, because the AT Protocol is not designed for interoperability, but rather for entrenching the silo owned by the main node (BlueSky) whilst giving the illusion of being decentralised. It’s to decentralised social media what Microsoft’s OOXML file format (tl;dr: a memory dump of Microsoft Word’s internal data structures encoded in XML, and useless to anything that’s not Microsoft Word or a very precise emulation thereof) is to open document formats.

It’s possible though less than ideal. Drivers that connect to devices are part of the attack surface, and probably the part you’d least want implemented in C when the rest of the kernel is in Rust.

There’s a Pareto effect when it comes to them, in that you can cover a large proportion of use cases with a small amount of work, but the more special cases consume proportionately more effort. For a MVP, you could restrict support to standard USB and SATA devices, and get a device you can run headless, tethered to the network through a USB Ethernet adapter. For desktop support, you’d need to add video display support, and support for the wired/wireless networking capabilities of common chipsets would be useful. And assuming that you’re aiming only for current hardware (i.e. Intel/AMD boards and ARM/RISC-V SOCs), there are a lot of legacy drivers in Linux that you don’t need to bring along, from floppy drives to the framebuffers of old UNIX workstations. (I mean, if a hobbyist wants to get the kernel running on their vintage Sun SPARCstation, they can do so, but it won’t be a mainstream feature. A new Linux-compatible kernel can leave a lot of legacy devices behind and still be useful.)

Drew DeVault recently wrote a simple but functional UNIX kernel in a new systems programming language named Hare in about a month, which suggests that doing something similar in Rust would be equally feasible. One or two motivated individuals could get something up which is semi-useful (runs on a common x86 PC, has a console, a filesystem, functional if not necessarily high-performance scheduling and enough of the POSIX API to compile userspace programs for), upon which, what remained would be a lot of finishing work (device drivers, networking, and such), though not all of it necessary for all users. Doing this and keeping the goal of making it a drop-in replacement for the Linux kernel (as in, you can have both and select the one you boot into in your GRUB menu; eventually the new one will do enough well enough to replace Linux) sounds entirely feasible, and a new kernel codebase, implemented in a more structured, safer language sounds like it could deliver a good value proposition over the incumbent.

Pete Waterman (the 80s pop producer behind Rick Astley) owns a small steam railway on his own land.

Based.