To achieve asic resistance, why not switch between a large pool of different algorithms sequentially, with their order and various parameters determined by the hash of the previous block?
1920x1080 at 3 bytes per pixel and 30 frames per second is 11GB for just one minute of video, and 186MB per second. That's far too big and expensive to stream, and outside of somewhat special circumstances I've never heard of anyone storing video in such a huge format.
> There's no good technical reason not to enable lossless compression
Why would you want to losslessly compress audio or video? The resulting files would be huge--often too huge to steam. Lossy compression is what you want.
You could put your propellers outside and away from the cage, with their motors inside the cage. This would also greatly reduce the size and weight of the cage.
"Why all these web workers and why should I care?"
"A: Language services create web workers to compute heavy stuff outside the UI thread. They cost hardly anything in terms of resource overhead and you shouldn't worry too much about them, as long as you get them to work (see above the cross-domain case)."