GuyNoIRQ
It doesn’t have as much to do with where the network stack is running, but that they’re leveraging hardware offloading. Their CPUs generally aren’t powerfull enough to switch packets at gigabit speeds let alone on many interfaces at gigabit or multi-gig speeds. Its by leveraging ASICs and maybe even some using FPGAs for hardware offload that they can switch packets at line rate. I understand how they do it, I still just find it kind of weird and cool.
I didn’t list HDDs as someone else had mentioned that already. I was just listing a few devices that weren’t mentioned in other comments yet.
Actually was looking into this some more, and came across this article.
https://hackaday.com/2019/06/10/running-linux-on-a-thermostat/
Possibly the antenna wasn’t tuned correctly to the channel which you have the router configured to use so you had a higher swr than your radio frontend could handle eventually burning it out.
Maybe just allow apt update specifically via the sudoers conf so you can cron job it to run without being prompted for user input, or just run it in cron as root.
What are the chances of an official flatpak getting maintained so us lazy folk don’t need to keep up with the GitHub repo/site for when updates drop?
Edit: Also do you have any plans to add NX support?
For 2.5" SSD I’d suggest a Samsung Evo or crucial mx500. These will top out at like 4TB afaik.
For 3.5" spinner I’d suggest an enterprise class HDD. Specifically WD Gold or HGST. Look up the most recent backblaze drive failure report for some models known to last a while.