Curious in general how often Youtube breaks things on their end, i.e. how long roughly this specific version of youtube-dl is expected to keep working without any active development?
git pull the repo, cd into it, and do `git log --follow -- youtube_dl/extractor/youtube.py`.
YouTube-DL Gitlab Backup Repository
11–20 of 37 posts
Re: YouTube-DL Gitlab Backup Repository
#12Gitlab is not immune to DMCA notices either since it's a US company. The RIAA probably won't try to take it down unless the youtube-dl development is actually relocated there or they become aware of it somehow. You'd have to host it in a country where DMCA can safely be ignored (anonymously of course), e.g. the Netherlands or Russia, if you want it to stay up reliably.
Gitee.com is a popular Chinese alternative. I'm pretty sure it'd be safe there.
[1] a collection of cases: https://github.com/HiddenStrawberry/Crawler_Illegal_Cases_In...
Re: YouTube-DL Gitlab Backup Repository
#13Re: YouTube-DL Gitlab Backup Repository
#14While this situation is a reason to look more closely at GitLab due to the ability to host your own instance, why not also look at a solution like Fossile: DVCS, wiki, and issue tracker all in a cross-platform, single executable file? https://fossil-scm.org/home/doc/trunk/www/index.wiki
https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w...
Re: YouTube-DL Gitlab Backup Repository
#15Earlier quoted context omitted.
Gitee.com is a popular Chinese alternative. I'm pretty sure it'd be safe there.
I don't think so. Youtube-DL can rip some popular Chinese VOD websites such as Bilibili and iQIYI, thus will first be "subjectable" to the Chinese equivalent of DMCA. 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 parti…
Gitee has hosted a youtube-dl mirror for years.
Re: YouTube-DL Gitlab Backup Repository
#16Earlier quoted context omitted.
git pull the repo, cd into it, and do `git log --follow -- youtube_dl/extractor/youtube.py`.
Thanks. That would indicate roughly 2 months or so...
Just spreading the repo around isn't going to help for very long.
Re: YouTube-DL Gitlab Backup Repository
#17How do you verify this isn't malicious? Who is running this repo?
Re: YouTube-DL Gitlab Backup Repository
#18git clone https://ipfs.io/ipfs/QmVJ6BtoavbWRJwWH8JmTd5Bf6i3zEzsecnBKTM...
Re: YouTube-DL Gitlab Backup Repository
#19I made a read-only backup on IPFS in the likely case it gets DMCA'd. 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.
Re: YouTube-DL Gitlab Backup Repository
#20Earlier quoted context omitted.
Gitee.com is a popular Chinese alternative. I'm pretty sure it'd be safe there.
China has extremely strict anti-scraping laws [1] so pointing out that youtube-dl is a tool that can be used to illegally scrape copyrighted data is likely to have the same effect as a DMCA takedown request with the same justification. [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.