Fortunately, we have saner heads at the EFF and GitHub to thank for this.   I do have two observations about this:

1.  The software has never been able to decrypt DRM.  When it encounters an actual encrypted stream, the software won't go any further.  This is the case with paid content from YouTube.

2.  None of this would have happened if the software stayed rather, um, well, geeky and difficult to use.  I've been using it for years building a config file that's over 70 lines long.  (some comments but lots of options for different situations -- then there's ffmpeg.)  It worked and its user-unfriendliness means it just did its thing under the radar and nobody really cared because of the limited audience.  Then some developers decided to build some front-ends that it made it more user-friendly but unfortunately, opened it to the masses where it got more mainstream attention.  Much like what happened when Usenet became much more mainstream.

But unfortunately, the RIAA is in the unfortunate position where it has to be perceived as having power so it really has no choice to flex its muscles once in a while and hope it's barking at low-hanging fruit.  In this case, that didn't happen.

To those of you who don't have a clue what this is all about, just go on your way, there's nothing to see here.  
 

Chrisphen wrote:

Peter the K wrote:

None of this would have happened if the software stayed rather, um, well, geeky and difficult to use.  
 

Perhaps, but the RIAA through its own ill-advised efforts has managed to promote the app far and wide.

Absolutely.  The Streisand effect in full force.