The total data on a CD-ROM including the error correcting redundancy exceeds 800 MB, or 6.4 Gb.

If you could imagine getting 1 bit from the optical disc per pixel (which is way too optimistic physically), you would need a 6 gigapixel camera focused super-precisely at the disc surface.

Looking at the problem from a different angle, Wikipedia says the features that store the data on the disc surface are about 800 nm (or about a micrometer) long. So to photograph them, you'd want to have pixels ideally smaller than a micrometer on each side. It's easy to check that an ordinary camera isn't achieving that kind of resolution without adding on external magnifying equipment.

Is it only because it would "look bad on MI5" if people like that worked there? Seems like such a trivial thing to immediately take a stand against and get rid of as soon as you notice it, rather than trying to hide

Does the answer vary depending on the programming language? E.g. Is the `Set<'e>` type in F# a functor?

The one thing that bothers me with traefik is that their implementation of ACME does not work if you have some sort of DNS load balancing. I had one setup with three servers responding to the same domain. It seems the first request )to start the ACME dance) would go to one server, and if the second one (with the .well-known address) is sent to a different one, it will just return a 404 and fail the whole thing. Now I either have * to delegate the certificate management to the service itself or add Caddy as a secondary proxy just to get certificate from it.

* Of course, someone smarter than me will point me to a better solution and I will be forever grateful.