

HeliBoard. However for swipe typing it’ll take some practice to get used to, it’s more sensitive to swipe accuracy and you may need to reset your muscle memory.
HeliBoard. However for swipe typing it’ll take some practice to get used to, it’s more sensitive to swipe accuracy and you may need to reset your muscle memory.
The other responses have so far talked about hardware setup, so I’m not going to do that. Instead I’m looking at your software setup: VMs can be comparatively power inefficient compared to containers, specially for always-on services that idle often.
Or they work in a regulated industry that requires pseudo-airgapped machines for remote users, e.g. the machine actually interacting with the systems needs to be within the controlled boundary but the company has a presence in multiple locations, so the solution is to have a Citrix server that the users remote into. But because the SSP also has access control requirements at every stage that take a long time to get updated to newest industry standards, the user still needs to have passwords rotated, MFA, and all that kaboodle.
The one thing snap does that flatpak doesn’t is provide CLI applications. But then nix also does that, so snap can go pound salt.
I used a Fractal Design case for a home server in the past. Pretty happy with them.
Depends on how you intend to maintain it. I started out with a Synology NAS. When that started to give out the ghost I built own so that I could have better control over the software and hardware. It’s now a NAS of Theseus - all the parts (even the OS) have been replaced over time, but it’s still the same “unit”.
The hardest part was deciding on a case. I started with a small form factor as a preference. Nowadays I just pick what gives me good airflow and ease in replacing parts.
Knocking is usually reads (from the header seeking), brrr is heavy writes.