Technical analysis of the RIAA claim against youtube-dl
This write-up follows the code paths in youtube-dl that get executed when you try to run it based on the claims of RIAA has put forward. This is a technical analysis, not a legal one.
Note: This analysis is based on one of the many unofficial copies of youtube-dl that have popped up during the last few days. I do not have a copy downloaded from the original repository and can in no way guarantee that these findings hold true for the original. However, given the complexity and the shortness of time it seems unlikely that someone went through the trouble of injecting the things in this analysis.
Credits: This analysis would not have been possible without the help of Jan Wildeboer.
As a reminder, RIAA uses the following argument to support their claim that youtube-dl is a tool primarily made for copyright infringement: