Earlier quoted context omitted.
Sure, but I'm trying to grok the essence of the technological measure being used by YouTube. I have to imagine that merely offering terms of service doesn't constitute a technological measure, and nor would merely slicing up the response in a DASH-like manner [0]. [0] https://en.wikipedia.org/wiki/Dynamic_Adaptive_Streaming_ove...
Well... here's the dumb thing. The DASH-like manner (or, "rolling cipher" as they like to call it) has currently held up as being an effective protection measure. It comes up all the time when RIAA in particular sues YouTube stream-rippers. https://torrentfreak.com/deciphering-youtubes-rolling-cypher...
Granted, I suppose the difference there is that the creators of those formats/protocols did publish the spec, whereas YouTube didn't. Or did they, though? The JavaScript that YouTube serves is the instruction for parsing the DASH response, available publicly, hardly different from publications like IEC 60908 ("Red Book" CD-DA spec) or an RFC 791 (IP spec) -- a different language, is all.
What a mess.