|
|
|
|
|
|
by cbhl
4261 days ago
|
|
|
1. Does the DMCA require GitHub to take down forks? AFAICT, it is up to the copyright holder to find and submit takedown notices for each copy. Plus, it's literally one click for a copyright holder to get a list of all direct forks for a repository. And if it becomes a problem, GitHub can just change the policy -- retroactively, even, if a particular incident makes it necessary. 2. This could be an abuse vector. Fork a popular repository, add some DMCAed content to it, and watch the parent get taken down. Or compromise the parent because it's old/unmaintained/abandoned and watch all the child forks get taken down. 3. Everything on the internet has legal fears. The question is, how much, and are you willing to tolerate that risk? |
|
|