RainyDayTmrw

Thanks for the information.

This sounds like something I would use HKDF for. But, to your point, it's nice to be able to build the design with a fewer number of primitives, and likely more performant, too.

This particular piece has been shared near me several times, in the context of this recent AWS outage, the previous big AWS outage, non-AWS outages, and others. Every time, I feel like I'm in vague agreement with the author, and at the same time, none of it is the least bit actionable. Even if Cook is correct, so what? There's no concrete change I can make in my working.

The edit window passed, so let me add: where and why one would use an extensible-output function in particular.

The nice thing about Blum-Blum-Shub or Blum-Micali is that they come with a proof of security. Even then, they tend to be impractical, due to performance and side channels.

This one is missing the most important part, the proof. Indeed, a sibling comment notes that empirical results look pretty flawed.

I freely admit, this is "smell" based speculation.

Can anyone share real-world examples of where and why one would use these, please?

This smells like self-dealing on the part of A16z.

Is there a parser ambiguity/confusion vector here?

I thought the same. Although, perhaps we have too few hatchways, and too much surface area inside each.

After a few dumb accidents involving header pins, I've come to the conclusion that exposed male header pins on my desk are a hazard.

As this is a tech forum, I expect that the name that stands out is Radio Shack, and I do agree that that story is tragic. For me, as a long time New Yorker, the other name that stands out is Modell's. They were, for quite a long time, a fixture in New York City and beyond. Even for us not sports inclined, we still knew Modell's as a reliable retailer of sneakers throughout the years. Arguably, their Covid era bankruptcy was already the end, and this was just private equity puppeting the corpse. Nevertheless, it's a sad and nostalgic story.

Kinda tricky. Last time this came up, the consensus was that approximately nothing commercially available supported RVA23 at the time.

The unemployment rate statistic is a bit misleading, because people who drop out of work permanently don't factor into it.

That's surprising. Why is there such a comparatively large number using 32-bit Firefox on 64-bit Windows?