I always liked the RP DNS record (https://www.rfc-editor.org/rfc/rfc1183) but no one seems to know about it or use it any more. The only reason my servers don't have one now is because route53 doesn't support it.

Its author was supposedly pretty good at algorithms. I think he may have even written a book or four about them. So I suspect it’s decently optimized.

Of course you’re technically right (you can absolutely write buggy code with Rust) but what others are saying (and what I have also anecdotally observed) is that Rust seems to have a much higher probability of new code just working (bug free) once you’ve cleared the compile step. The only language I’ve used that worked like that was ocaml and maybe Haskell (though I only dabbled in that).

The problem is that if you consider Discovery non-canon then it has to follow that Strange New Worlds (which spun off from Discovery) is also non-canon and that would be a shame. It (and Lower Decks) are the only new Trek shows that feel like they actually truly understand Star Trek.

according to what i think i read here, Lower Decks revealed that Discovery was on another timeline, so in that sense it would remain canon (for that timeline) and just would not effect the prime timeline

Thing is, Strange New Worlds is a direct continuation of Discovery, and Strange New Worlds had a same-universe time-travel crossover with Lower Decks.

They cleared up the TOS Klingons discrepancy in an episode of Star Trek: Enterprise (Season 4 episode 16, “Divergence”).

The original comment was not about traditional packaging, it was about Nix which is different (and immutable in its own way).

Wouldn’t “x”.join(…) be enough?

Possibly not:

  "x".join({'aa'+'bxb'}) == "x".join({'aaxb','b'})

The separator should not be able to show up in the inputs.

This is why I raised an eyebrow when TFA wrote,

> When I saw this, I wondered why it has several inner hashes instead of using the raw string.

The inner hash constrains the alphabet on that portion of the input to the outer hash, thus easily letting you use a separator like "," or "|" without having to deal with the alphabet of the inner input, since it gets run through a hash. That is, for a very simplistic use case of two inputs a & b:

  sha256(','.join(
    [sha256(a), sha256(b)]
  ))

If one is familiar with a git tree or commit object, this shouldn't be unfamiliar.

Now … whether that's why there was an inner hash at that point in TFA's code is another question, but I don't think one should dismiss inner hashes altogether.

I could see an attack vector here based on file/directory names or the full path. Different inputs could lead to the same order of enumerated checksums.

I'm not dismissing them, inner hashes returning a hexadecimal string fulfills the "the separator should not be able to show up in the inputs" constraint.

Thanks—that makes sense. I was struggling to come up with an example that would fail but I was just unconsciously assuming the separator wasn’t showing up naturally in the individual parts instead of explicitly considering that as a prerequisite.

Only if you can guarantee it that possible for someone to sneak in an input that already contains those "x" characters.

I use emacs so that meant practically every prefix character would annoy me at some point. I ended up using C-\ since that almost never gets used by anything (I was surprised it could even be detected by terminals).

C-\ is one of my favorite Emacs keybindings :). You use it to change input methods, in my case to write e.g. Greek letters and other Unicode symbols in plaintext files using TeX notation.

I sometimes like to program using Unicode variable names when doing physics/math, and this is an easy way to do so built into Emacs.

I just checked my .screenrc and while I don't have a date in it, the file was last modified in 2010. But that's around the time that I switched to tmux. I've been _very_ happy with tmux over the years…

Looking over the screen 5 release notes it's hard to tell what I've missed being out of that world over the past 15 years. Does anyone have a good rundown on their current differences?

I used this exact same keyboard and ADB adapter until 2017 (probably 15 years). I only got a new keyboard when I wanted N-key rollover for games. I love the feel of that keyboard a whole lot and tried to get something similar with my new one.