I imagine they have to lock / disable all forks beyond what the notice mentions as well, unless Sony, et al don't understand how git/github works.
I imagine they have to lock / disable all forks beyond what the notice mentions as well, unless Sony, et al don't understand how git/github works.
Just consider Youtube a moment. Couldn't they minimally run a hash on any uploaded/embedded sound and see if it matches the hash of some taken-down material before? It'd probably catch at least a significant number of users even if it's trivial to bypass and susceptible to compression losses and quiet-extensions and so forth. (An AI could always "listen" to it though and probably perform pretty well.) Anyway, Youtube doesn't make an automated effort to take down infringing material (that I know of) so I don't see why Github has to.
You don't have to do any forensics in the sense of your youtube example, you just have to follow the graph.
Whether that it is a legally compelling point, I have no idea.