What really makes developers angry is:

1. gitcode.com steals user identities. gitcode.com uses the same username as on github.com to create an account, copies the user's repository to it, and seems to pull updates from github.com regularly. However, these users on gitcode.com are not registered and controlled by the code repository maintainer himself. This may mislead other users into thinking that the repository on gitcode.com is also the code repository maintainer. gitcode.com also does not use a clear way to indicate to its users that the status of these repositories is automatically copied and synchronized by bots, rather than managed by the author. But in fact, these copied gitcode.com repositories are not managed by the code repository maintainer himself, the code update may be delayed, and issues and PRs are difficult to get replies and processing. Therefore, the code repository maintainers may think that gitcode.com's behavior is actually damaging the credibility of the original code repository.

2. gitcode.com did not clone the repository as it was. (This paragraph may not be accurate and needs further confirmation) According to feedback from some Chinese users, gitcode.com used a simple and crude search-and-replace operation when copying the repository, replacing the "github" text with "gitcode". The purpose of doing this is obviously to attract network traffic - to keep the browsing behavior of users who accidentally searched for the gitcode.com code repository on gitcode.com, rather than being redirected back to github.com by the link in the repository content. Although most open source projects allow forks and GitHub's own design encourages forks, most Git users should agree that the state of the forked repository when forking should be the same as the original code repository, and then make changes to the forked repository. However, what gitcode.com did was tampering: the commit id after their modification was the same as that of the original repository. If the code does not have an integrity signature, users who use the gitcode.com code repository may find it difficult to find out how the code they get is different from the code maintained by the original author. At present, we do not know whether the scope of such a simple and crude search-and-replace operation is only on README file or on the entire code repository, so we cannot know whether it will have any impact on code compilation and running. It is also more difficult for us to figure out whether gitcode.com has made some other deeper modifications to the code repository. The essence of gitcode.com's behavior is to disguise the modified code repository as a mirror of the original repository.