[rhino369]

But once they get a takedown notice they have actual knowledge that the material is infringing. If there is a fork that they know about, they do have actual knowledge. They have been doing it in the past, and if they now try to make sure they don't know about forks, that is willful blindness and they will still be found to be infringing.

512(c)(1)(a)(ii) has the so called "red flag" requirement. "n the absence of such actual knowledge, is not aware of facts or circumstances from which infringing activity is apparent"

Essentially, if they know about a fork and a reasonable person would know it is infringing, they lose their safe harbor.

Does GitHub have in house counsel? This policy is risky and doing it response to an outcry about actual pirate programs this will look horrendous if they end up in court.

[fernandotakai]

from what i understood they have knowledge of the fork, but they don't have knowledge if the fork also contains copyrighted material -- so, if i fork x and i remove all the supposedly copyright stuff, my fork should be ok.

[rhino369]

Under the red flag requirement, they got to at least check or think about how identical the fork is.

Yea, if you fork Linux and your fork just happens to use a stolen logo. Obviously there is no reason to think Linux is infringing.

But if you are forking popcorn time, that is unreasonable to assume that the fork is going to be non-infringing.

A general assumption that forks are okay is not a reasonable assumption. They'll have to look at this on a case by case basis.

This is even easier when the infringing content is a file or code. There is no excuse for not removing the infringing file from all github projects. And it is easy to check the forks for containing the alleged infringing code.

The safe harbor is not there to protect people acting in bad faith.