airgapped

I definitely learnt (more than) a few things from your write up, thank you sir!

It is complete overkill for most home server tasks but I would look to run something like this for next 10 years at least so I can see it making sense if you cost it out like that.

Depends on your personal use case of course but for comparison I have a (relatively) piddly Intel N305 processor mini PC with 16GB of memory and currently run a 25-30 container load, including Plex and a torrent server. My setup currently idles at around 20% CPU and 25% memory utilisation, so I can quite confidently say the linked N5 ought to give more than enough headroom to handle a typical homelab/self hosted load.

Death death to the IDF

Don’t mean to outright negate the article but I have experienced literally none of the problems mentioned with Wayland through three separate installs over more than 2 years. I happen to be running a nightmare of a setup too (nvidia/AMD GPUs in a laptop)

Put first episode on max priority + download sequentially. Go make a cup of tea. First episode is ready to stream. Do same to second episode before you start watching the first and Robert is your father’s brother (Bob’s your uncle).

Today I learnt, thank you.

Question please, how would podman alleviate container update woes?

I tried many different keyboards but honestly nothing matched up to SwiftKey, now sadly owned by Microsoft, so I locked its internet access using RethinkDNS (or NetGuard)

It is always the ones you least suspect.