I’m pretty sure every microwave just splits the input in to the last to digits as a number of seconds and the digits before that as minutes. Then runs for 60 * minutes + seconds. So 0:99 is equivalent to 1:39 and 1:80 is equivalent to 2:20. I mean it is a little weird that the seconds can be >59 and extra weird that you can do 6:66 but it isn’t exactly wizardry.

YAML is fine as a configuration language and ok data input language.

YAML is absolutely cursed as a programming language. As in Ansible has created a really shitty programming language inside of YAML. Should be burned with fire.

The short answer is that Docker (and other containerization technologies) share the Linux kernel with the host. The Linux kernel is very complicated and shouldn’t be trusted to be vulnerability free. Exploitable bugs are regularly discovered in the Linux kernel (and Windows and Darwin). No serious companies separate different tenets with just container technology. Look at GCP, AWS, DigitalOcean… they all use hardware virtualization which is much simpler and much more likely to be secure (but even then bugs are found on occasion).

So in theory it is secure, but it is just too complex to rely on. I say that docker is good for “mostly trusted” isolation. Different organizations in the same companies, different software that isn’t actively trying to be malicious. But shouldn’t be used to separate different untrusted parties.

IMHO Arch is actually a great choice. They do have a minimum update frequency you need to maintain (I don’t recall exactly, I think it is somewhere between 1 and 3 months) but if you do, and read the news before updates (and you are usually fine if you don’t, usually the update will just refuse to run until you intervene) things are pretty seamless. I had many arch machines running for >5 years with no issues and no reason to expect that it would change. This is many major version updates for other distros which are often not as seamless.

That being said I am on NixOS now which takes this to the next level, I am running nixos-unstable but thanks to the way NixOS is structured I don’t need to worry about any legacy cruft accumulating from the many years of updates.

And after all of that I don’t think it really matters. I think any major distro you pick, weather stable, release-based or LTS will be fine. They all have some sort of update path these days. (unlike in the past where some distros just recommended a re-install for major updates).

I hope they are using more than just docker for isolation 😅 Each user should be running in a different VM for security.

Just desserts

Strongly reminds me of Old MacDonald Had a Barcode, E-I-E-I CAR. Basically put a standard anti-virus test string into various sorts of barcode and see what breaks.

the reason no one posts the bitrates is because it’s not exactly interesting information for the the general population.

But they post resolutions, which are arguably less interesting. The “general public” has been taught to use resolution as a proxy of quality. For TVs and other screens this is mostly true, but for video it isn’t the best metric (lossless video aside).

Bitrate is probably a better metric but even then it isn’t great. Different codecs and encoding settings can result in much better quality at the same bitrate. But I think in most cases it correlates better with quality than resolution does.

The ideal metric would probably be some sort of actual quality metric, but none of these are perfect either. Maybe we should just go back to Low/Med/High for quality descriptions.

The worst part is that this doesn’t seem to be some sort of better quality. All of the other qualities seem to have tanked in the past year, so at best this just restores the previous 1080p bitrate.

Yet another service to maintain. If the server is crashing you can’t log in, so you need backup UNIX users anyways.