The mistake is forking and hosting it on GitHub. If Haier sends GitHub a DMCA takedown notice, they will comply, and the forks will be deleted too. Use other hosting services for redundancy and keep a local copy.
Good point. Nothing in the article explicitly states that it’s a copyright claim, but they do mention “protecting… [their] intellectual property”. In any case, it’s always easier for the website host to fold to cover their own asses than to continue hosting the content.
The mistake is forking and hosting it on GitHub. If Haier sends GitHub a DMCA takedown notice, they will comply, and the forks will be deleted too. Use other hosting services for redundancy and keep a local copy.
I don’t think there’s a copyright component to this. DMCA isn’t on the table
Haier were implying that they might sue if the developer didn’t take it down
Good point. Nothing in the article explicitly states that it’s a copyright claim, but they do mention “protecting… [their] intellectual property”. In any case, it’s always easier for the website host to fold to cover their own asses than to continue hosting the content.
The letter from haier says it is a beach of TOS. It’s directly a “take it down or we’ll delete your account” letter