It's a catch-all in case any single service is badly configured. This often happens while people are fiddling around trying to configure a new service, which means they are at the most vulnerable.

> I heard Nix is a great way to build containers though.

It is, I'd recommend the fantastic https://www.youtube.com/watch?v=6Le0IbPRzOE to appreciate some major differences.

That sounds like hundreds of hours of work.

Or a few hours writing a script of they are well formed. (Possible even less using AI).

Did Pinboard get bombed by HN?

> Error: Connection refused

Hopefully coming soon to your favourite distro: https://github.com/NixOS/nixpkgs/issues/341665 :)

Self-posting this, mostly to hear if there's anything wrong or suboptimal about this solution. I've been using Nix for a bit, but I'm almost completely new to Rust.

I assume so, because I've done it (repeatedly) and there's never any glue involved. The Billy book cases used nails for the back board, but it's easy to get those out by tapping the board from the front.

> easy to get those out by tapping the board from the front.

Or just pushing something to the back of a shelf in my experience. Billy's biggest fault I think.

Some of this looks real bad though, like `if !found … else …`. Why the double negative, when you're going to have both branches anyway?

You put the happy/hot path in the if case and the else is the abnormal/less usual path.

On NixOS, set

  programs.firefox.policies.Preferences."dom.private-attribution.submission.enabled" = false;

(https://gitlab.com/engmark/root/-/commit/bbb3ff9efb878ddda38...)