They are not too terrible really. 3rd gen i7 is the Ivy Bridge generation, so 22 nm. For many homelab server tasks the CPUs would be just fine. Power efficiency is of course worse than modern CPUs, but way better than the previous 32 nm Sandybridge generation. I had such a system with integrated graphics and one SSD and that drew 15 W at idle at the wall.
No, the original Pi Zero uses the CPU of the Pi1 (only clocked higher). So it is quite a bit slower than a Pi 2, since it has only a single ARMv6 CPU core. Still fine for a DNS server on a typical home network.
You can easily mirror Github wikis as well. You just need to add .wiki.git to the repo URL. That way you can clone the wiki just like any other Git repo.
Perhaps a Raspberry Pi 500 (or the older Raspberry Pi 400), can do all the things an ordinary Raspberry Pi can, but comes as a complete device with built-in keyboard. Runs Linux and is rather easy to use.
There is also AMD and they are doing pretty well. I wouldn't write off x86 just yet. But less competition is never a good thing, and Broadcom buying another company has never resulted in anything good, as far as I can tell. For anyone except Broadcom themselves.
It is, but Signal and Matrix aren't really all that similar. Matrix's privacy is pretty atrocious. It stores tons of meta data about users all over the place. That's the exact opposite of what Signal does.
Sure, if you have exactly one client that can access the server and you can ensure physical security of the actual network, I suppose it is fine. Still, those are some severe limitations and show how limited the ancient NFS protocol is, even in version 4.
You need sampling at twice the frequency as a minimum to extract a time domain signal into the frequency domain. It says nothing about “perfect” especially when you’re listening in the time domain.
Yes it does. You can use a higher frequency, but that does not change anything except increase the maxiumum frequency possible.
Even with perfect ears and the best equipment, there is no audible (and mathematical) difference to be had.
Everyone who claims otherwise should watch Monty's explainer videos. I know they are quite old at this point, but everything he explains is still perfectly valid. If that does not convince you, nothing will.
It turns out that dynamic range is limited by the audio sampling rate and the human ear can easily detect a far greater range CD audio supports.
Dynamic range isn't limited by the sampling rate. It is limited by the resolution, which is 16 bits for the audio CD. With that resolution you get a dynamic range of 96 dB when not using any dithering and even more than that when using dithering. Even with "only" 96 dB that dynamic range is so vast, that there is no practical use of a higher resolution when it comes to playback. I know that the human ear is supposed to be able to handle 130 dB or even more of dynamic range. The thing is, you can only experience such a dynamic range once, afterwards you are deaf. So not much point in such a dynamic range there.
There are good reasons to use a higher resolution when recording and mixing audio, but for playback and storage of the finished audio 16 bits of resolution is just fine.
If someone compromises the host system you are in trouble.
Not only the host. You have to trust every client to behave, as @forbiddenlake already mentioned, NFS relies on IDs that clients can easily fake to pretend they are someone else. Without rolling out all the Kerberos stuff, there really is no security when it comes to NFS.
Does such a thing exist? Ordinary flash storage is pretty bad at keeping its content when powered off for a long time, due to how flash memory works. I'd be curious about such drives.
or a domain with a random string of characters so no one could reasonably guess it? Does it matter?
That does not work. As soon as you get SSL certificates, expect the domain name to be public knowledge, especially with Let's Encrypt and all other certificate authorities with transparency logs.
As a general rule, don't rely on something to be hidden from others as a security measure.
They are not too terrible really. 3rd gen i7 is the Ivy Bridge generation, so 22 nm. For many homelab server tasks the CPUs would be just fine. Power efficiency is of course worse than modern CPUs, but way better than the previous 32 nm Sandybridge generation. I had such a system with integrated graphics and one SSD and that drew 15 W at idle at the wall.