Yeah, stat'ing the file in a tight loop until no-growth is attained, is the way I would do it. But to be honest, I wanted to leave the code purposely ineffective so as not to teach people how to do DoS attacks. :-)

The node probably should be renamed "A way to save YouTube videos to disk".

I suspect the engineers at YouTube are probably already working on a way to stream to multiple cache files for a single video, so as to render this method obsolete. But, for the time being, it does offer a way to locally save youtube videos to disk, which is useful for archiving and offline viewing. I will post an example with a save button later, after I test how the file buffering goes.

I'm sure someone smarter than me out there, would know how to detect the progress of the on_load javascript request, as well as the cws file they send as a pre-loader, to the actual video. There seems to be alot of signals which one can tap into.