-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encourage Forking in Protest #3
Comments
The best protest is to move to other alternatives like gitlab, bitbucket. |
THANK YOU SO MUCH FOR PUTTING THIS BACK UP I LOVE WHOEVER DID THIS <333333 |
Please, everyone needs to fork and download this. Self host it on GitLab, self-host it on a website, just make sure that they cannot silence us all! |
for download youtube-dl source code from youtube
encoding and decoding Edit; |
100% I say maybe we start our own github... |
I did started sharing on twitter and reddit |
I am not sure what the plans are for the original developers but hopefully other developers will be able to help maintain it.
My only problem with this is then they would have won. I think having everyone replicating this repo across github is a much better form of protest. I have always used GitHub and I'm not about to stop because of some bad decisions made by the RIAA. I am not going to move when ever their gaze causes interruptions, I would prefer to stand my ground. |
No. Fork it here, fork it to gitlab, fork it to bitbucket, fork it to sourcehub, fork it to codeberg, fork it to gitea, create codesandboxes, repl.it's, paper-print it and drop them all over the place... |
Leaving github will hurt them financially. Copying the repository everywhere is an intellectual reaction. |
The original repo is surely stored in the Arctic vault anyway |
The stars and forks are going on, I honestly do hope they don't try to follow this in court, but at least find a way to have it in some central place where they can do bug fixes and keep developing, and at the same time receive support |
I hate RIAA. Thank you for doing this and standing up to them. |
This is nothing 'unprecedented'. These guys have been fighting the emergent distributed/cooperative society, for a long time already: |
This is a total crock |
Forks don't matter unless the code is kept current. Expect the main youtube-dl project to itself be attacked from the hosting and domain levels. The main developers may themselves be attacked. Eventually YouTube will be making changes and youtube-dl will stop working. When various forks and various patches (of varying and dubious quality) become scattered throughout them, and maintainers and "maintainers" decide on code style changes which make comparisons and coordination difficult, things will slide downhill. Forking is not protest. Coordinating issues/tickets and pull requests across those forks is. Furthermore..
and so.. https://github.com/github/dmca/tree/416da574ec0df3388f652e44f7fe71b1e3a4701f |
I actually laughed hard with pull requests on that last one, seriously advise anyone to go and see. |
Yeah well... think of it more like a true act of decentralization, they can eliminate one node of a dht, however there are so many copies with the exact same git history, that it's virtually impossible for them to just erradicate this software. And that must hurt a lot. Who will be faster, google engineers trying to come up with a new cryptographical paradigm that still enables for all kinds of devices and bandwiths to consume that content, or the whole fucking world of developers with a collective mindset? :-) And I bet you mr Bill must be laughing his ass off at mr Google, and these Warners, Disneys, Universals... I mean the guy practically invented proprietary software, and capitalized it the most. Now he owns the biggest "free" open source hub... |
RIAA's decision to remove youtube-dl from GitHub sets a dangerous precedent for open source software on the internet. Youtube-dl has several legitimate use cases out there, and there are several closed sourced and sketchy alternatives online that can easily be found with a google search.
Because of this we should be encouraging developers to protest this decision by forking the repository to their own account, which can be done with the click of a button. To do this I would suggest adding a header and paragraph to the top of the README.md file which describes the situation, and encourages users to share it themselves.
The text was updated successfully, but these errors were encountered: