hvenev

The website checks the Referer.

This blog post calls libgit2 "git's C library" as if it is in any way related to git. I don't think it is.

> In the meanwhile in raspberry pi land, you can just go to download a reasonably new OS image from their website anytime you want and it will run on all their models.

Are you saying that even with the Raspberry Pi we are still at the mercy of the hardware manufacturer when it comes to OS images?

I personally call this process of setting up a new device, whether for me or for someone else, "shit shoveling". It is something of a ritual.

In the former case the thing that needs to be removed is the entirety of the OS (and if that proves to be impossible, the device is returned or discarded), and in the latter it's a scan of all apps and removal of all unnecessary apps, my grandma does not need Samsung Galaxy Games, thank you very much.

Will you not have `~/.ssh`? If you have `.ssh .config/ssh` as a rewrite rule, `stat ~/.ssh` will still find it.

For IPv4 the graph does not start at zero, but at around 45K.

> Jeff once simultaneously reduced all binary sizes by 3% and raised the severity of a previously known low-priority Python bug to critical-priority in a single change that contained no Python code.

This sounds really plausible. A change to the C toolchain/library (for example, specialized/inlined memcpy) may affect binary sizes significantly, and may change the behavior of something the C standard leaves undefined (for example, memcpy with overlapping arguments).

Back when my job involved using Kubernetes and Helm, the solution I found was to use `| toJson` instead: it generates one line that happens to be valid YAML as well.

From what I remember, the quality of a safe is measured in minutes, with "15-minute" safes being OK for general use.

English also changes, so the only way to be safe is to quote all identifiers.

What I personally do is

    User=per-service-user
    ExecStart=!podman-wrapper ...

where podman-wrapper passes `--user=1000:1000 --userns=auto:uidmapping=1000:$SERVICE_UID:1,gidmapping=1000:$SERVICE_GID:1` (where the UID/GID are set based on the $USER environment variable). Each container runs as 1000:1000 inside the container, which is mapped to the correct user on the host.