So where is the development continuing with all this?
That issue tracker was a great way to lose faith in humanity, just from the sheer number of people who couldn't follow instructions to search for existing issues before opening new ones, or to provide all the answers the issue template asked for.
Get the developers to never look at a bug unless it has the "triaged' label. Then have trusted volunteers who read each bug, assist the bugreporters to get stack traces and whatever is necessary, dedup, and then finally apply the label.
It's a good task for people who have some technical expertise but aren't yet confident to be submitting their own PR's.
Duplicate stack trace? Close and link. Missing relevant info? Close.
It supports dozens of sites btw. That's what I'm specifically referring to.
I think you are overestimating the amount of repositories that are affected by DMCA takedown threats (erroneous or legit).
However given that i work on some P2P services that could be argued scrape and/or distribute, i'm heavily debating moving. A nice host for a potential employer to view is not worth being DMCA'd.
I hope this causes a lot of additional desire to decentralize these portions of the dev workflow stack. Potential solutions exist, but no one cares.. i hope we collectively start caring more, and adopting solutions.
If you want to escape US law, feel free to use gitee.com located in China. Or, push your politicians to change the laws.
Microsoft has no way of overcoming the DMCA law themselves, other major companies have continued to lose lawsuits. It doesn't help that mega monopoly entities like Disney want it to stay taht way and will bribe politicians and others.
...assuming the DMCA request was valid. Some commenters in earlier HN threads were arguing that it wasn't.
The ban on circumvention tools allows for a claim in civil court, during which a judge may restrict availability of the program.
I, for one, heard a few too many times "this was the last straw" for every single privacy breach that happened in the past decade and resulted in no meaningful change for the better, so I find it hard to take this kind of statements seriously anymore. Is there any kind of basis that you'd like to provide for your speculation?
I think it's because it's a stretch of the law and can then abused to block a LOT more.
I still think it is bullshit (and so is DMCA) but that is how the law is written.
eg if you clone that repo, and run
git log --show-signature 34299510b
That said, I have been able to find clones of the youtube-dl repo elsewhere with HEAD 416da574e, and the 3 commits the gitlab repo adds on top of that seem innocuous.
git log -p 416da574e..HEAD
The original author moved to gitlab and started GPG signing commits with his real GPG key. This gives packagers certainty they can replace old github links with new gitlab links, it tells us this project hasn't been compromised and is safe to be redistributed, unlike blackjack4494/yt-dlc
Signed commits from them go back at least 1 year. So its not "started", but rather "continued" signing.
I'm not totally sure which tool I should use, but I'm leaning towards the fork, because it has more support in general, and has fixed things faster.