zlacker

>>linker+(OP)
The two subject repos are:

  https://github.com/Andre0512/hon
  https://github.com/Andre0512/pyhOn

Make whatever use of that information you will before the takedown occurs.

>>sokolo+xa
If people fork the repo, would they also be sent a takedown?

>>Action+Ef
If you fork it, do a proper git clone and git push. Github can and has DMCAed direct forks in the past.

>>aaomid+xg
At the risk of asking a dumb question, what does a git push do for you there? (Fully agree on the clone locally point.)

>>sokolo+ah
If Github doesn't realise you forked the project, it doesn't appear in the list of forks, which a lot of companies use when sending an actual DMCA notice to Github.

I'm not sure what you'd need to do to disconnect your fork, but clicking the "fork" button will often get your repo automatically taken down if the parent repository gets DMCA'd.

If the commit history is different (say, because you rebased the project onto a slightly different initial state), Github won't auto-detect the fork as easily, so the lawyers would need to find your project and include it in their takedown notice.

>>jeroen+Bk
When I read ‘git clone’, I assumed “on the command line of a machine you control, run git clone” not “use GitHub’s repo fork web interface action”.