Credit cards explicitly do a type of forwarding so that your old subscriptions continue to work if you get a new card. If you ever tell your bank that you've lost your card or had it stolen then they will reissue it differently without that "forward" feature, to prevent fraudulent activity. I learned this when I had fraudulent activity on my card and they accidentally did a normal reissue, and so the fraudulent activity continued even after I got the new card.
Yeah, Quick Look’s are what brought me to Giant Bomb initially. They aren’t reviews and they take pains to not spoil too much of the game. They give a good feel of what the actual gameplay looks like, which is almost never available from the game trailers, and which I find is hard to get a good mental picture of from written reviews (especially short ones).
Just watching their quick looks introduced me to so many different game genres that I’d never tried before. It’s a shame they stopped doing those a couple years ago.
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.
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
> 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.
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.
