Yes, double danger. 😄

sorry, "spec doesn't say" i.e. it doesn't require it. heh. thumbs..

NFS is 30 years of accumulated ad-hoc behaviours like this. you can see why the "bake offs" were so critical back in the day.. good times. (I last worked on this stuff for early NFSv3, a thankfully the trauma has mostly been forgotten! lol)

if cookieverf is not properly reset when cached directory data is invalidated, readdir calls may send a non-zero cookieverf with a zero cookie, loop city.. the spec say but some servers expect cookieverf=0 to signal a fresh directory read. or maybe swap some bytes and force the matter. :)

My vague memory is that the original sin here was intentional as a cache busting hack because of the problems with cache invalidation on some linux filesystems (I want to say JFS but might be remembering wrong) during readdirplus operations. you do a 'stat' during that and you could end up looping.

This is nuts, wow, had no idea

Not sure. Got bored? Watched YouTube instead?

I have used that line sooooo many times and been met only by blank stares. We live in an uncultured age.

How it's going:

❯ git log | grep refactor
refactor: switch theme persistence from localStorage to sessionStorage
refactor: Extract and centralize post metadata processing into a shared utility function.
refactor: improve type safety with shared Post types

The amount of work that goes into a clip like this.. give it 5-10 more years, 2010s era video will be as unbearable to watch as 70s TV is now just because of the pacing evolution.

would be great to see TikTok/Insta content with these!

Great piece. The “risks” section in the CoreWeave S-1 will be talked about for decades.. Epic barely begins to describe it.

In retrospect I think we’ll say transistor density was simply the first expression of the phenomenon. Or maybe it always does just reduce down to transistor density and it will continue to be the signal…. 🤷‍♂️

I'm assuming some of these are so high (again, it's less than 6hrs of data!) from a client retrying some number of times after failing due to the DNS block.