Magisk on Windows Subsystem for Android project is banned from Github
Frequent users of the Windows Subsystem for Android should know Magisk on WSA, a project dedicated to providing Magisk for the Subsystem for Android and then rooting.
However, the project has now been banned by Github. Currently accessing the project will prompt that the repository has been closed. The reason is that it violates GitHub’s terms of service.
Is it possible that Microsoft or Google filed an infringement complaint and asked Github to remove it because of copyright issues? The possibility is extremely low or not, because the mark is a violation of the terms of service agreement. If it is a copyright issue, it should be marked with a DMCA notice, and the DMCA notice can be queried for the specific situation, including the copyright owner who initiated the complaint.
So how does Magisk on WSA hosting repositories violate the agreement? This is about the construction method provided by the developer. The developer does not provide a direct installation package but requires users to compile it through the Github Actions service, which means that each additional user requires an additional fork and occupies the resources of Github Actions.
If it is a normal service, it is fine to use Github Actions, but this kind of purely letting users perform automatic compilation by themselves does make Github a bit uncomfortable. The number of forks of the project exceeds 110,000, which means that at least 110,000 users fork and use Github Actions to compile.
This kind of behavior is already abusing Github Actions. The compilation process requires a lot of Github resources. Therefore, it is reasonable for Github to ban the project on the grounds of violating the terms of service.
At present, there are still many Forks on Github that continue to provide operation methods for using Github Actions, and it is estimated that these may also be banned in the future. If the developer provides a method to guide users to download to local compilation without occupying Github resources, it is estimated that the project can be restored.
