But to me as a long time Gitlab fan this shows the power of using Gitlab. Because if they were using Gitlab when the DMCA hits they could have easily migrated to their own Gitlab instance.
While Github would have to export things into another format. I'm sure people have worked on exporting data from Github to Gitlab but it seems much easier to just use Gitlab.
Edit: And of course besides data, you can't migrate contributors as easy. Which is also where Gitlab is powerful because it's open source and people are actually discussing federation in it. I doubt Github will ever get any kind of federation outside of microsoft services.
Not sure if I would do that. Wouldn't that make me directly a target for the companies issuing the DMCA?
Yes, if you host this anywhere without safe harbour protection you're going to get the DMCA takedown directly
[1] a collection of cases: https://github.com/HiddenStrawberry/Crawler_Illegal_Cases_In...
It might be the case, but the repo you linked doesn't support that claim very well, and the cases cited are largely irrelevant to the case at hand.
"Forbidden area #1: providing scraping-related services to criminal organizations". Three cases listed. The first is one programmer's personal account of being arrested, which is very scant on why; the only info I can glean: "I developed some sort of ML API which is then used by a criminal enterprise against some influential company for god knows what purpose". Hard to draw any conclusion from that. The second case is ML-based CAPTCHA bypass for credential stuffing against Tencent QQ, emphasis on credential stuffing. The third case is some sort of black hat SEO campaign against Baidu, the scraping part (if any?) doesn't seem central to the conviction.
"Forbidden area #2: scraping and sale of personal info". Common sense, irrelevant.
"Forbidden area #3: commercial use of unlicensed business data" and the following untitled category list three cases, all of which are mass scraping operations either from a business competitor or that seriously affects site operations (through aggressive scraping).
AFAIK there are a lot of low hanging fruits in the Chinese piracy scene not yet targeted, and there are enough small-time commercial operations involving copyrighted media products begging to be taken down, it's highly unlikely anyone will bother to target some high-barrier-of-entry tool mostly facilitating the download of otherwise public videos.
Worse, these companies are often backed/protected by powerful figures (often under the umbrella of some influential state members) and under such power, these kind of "threats" will be eradicated very efficiently, especially with Bilibili which is partially "state-monitored" (not sure if sponsored) due to the presence of the channel of the official youth branch of CCP is opened there [1].
Thus, relocating your repository to gangs aren't safe at all.
A rule of thumb: The prerequisite for your business to survive in China is that you need to have powerful affiliates, and make sure you do not piss off that powerful guy.
[1]: https://space.bilibili.com/20165629?from=search&seid=1277417...
Gitee has hosted a youtube-dl mirror for years.
git clone https://ipfs.io/ipfs/QmVJ6BtoavbWRJwWH8JmTd5Bf6i3zEzsecnBKTM...
There are Git-backed distributed issue trackers like Git-bug https://github.com/MichaelMure/git-bug (and probably other tools) that should be more used.
One could perhaps convert Github issues to git-bug and store on a branch of this IPFS Git repository.
There is a Github bridge that will import the issues (including the complete history). PRs are not supported yet though.
https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w...
Just spreading the repo around isn't going to help for very long.
> the hashes from the old "true" repo.
Isn't it just SHA1? I think it's generally accepted it's not secure...
Also it would be quite easy to build a clone repo that looks the part with all the correct hashes, the git "database" structure is quite simple.
