How does it work anyhow? It must do more than `wget` the mp4
YouTube-dl source code encoded in two images
61–70 of 110 posts
Re: YouTube-dl source code encoded in two images
#62Re: YouTube-dl source code encoded in two images
#63Use Pillow to read the pixels from each file, and write the RGB values to a new file. Then use the gzip library to uncompress that and create a TAR file. Then I just viewed the TAR file in The V File Viewer.
I stopped there because that was enough to show that it worked. I have ImageMagick installed somewhere, but this was more fun.
Re: YouTube-dl source code encoded in two images
#64This recent takedown will only make more people know about YouTube-Dl and hopefully create more forks. When will these big companies learn!?
Re: YouTube-dl source code encoded in two images
#65Side Question : Is there a distributed alternative to github ?
Re: YouTube-dl source code encoded in two images
#66How does it work anyhow? It must do more than `wget` the mp4
Re: YouTube-dl source code encoded in two images
#67Re: YouTube-dl source code encoded in two images
#68Earlier quoted context omitted.
I'm not sure if this is a joke, but I'll humor you. Yes - it's called git.
I’m not sure if this is a joke, but I’ll humor you. GitHub is way more than git.
Meanwhile there is a federated git as a reference implementation called Forgefed.[2]
Re: YouTube-dl source code encoded in two images
#69Genuine question, how viable is it, if we (code monkeys) created some sort of a blacklist of the entities that are not allowed to use our open source projects? -- something like "We don't support Internet Explorer" but a bit more aggressive? like "These entities don't understand the Internet, we don't support them, they cant use our software"? Maintaining that list would be a ton of work and edge cases tho :/
Do you really want to live in a world where software is politicized to the point that FOSS devs are maintaining shit-lists of undesirables barred from using basic tools? It won't end well, and the adverse effects will disproportionately impact people without power, not the large companies you have in mind.
Software is already political. Commercial software traditionally does this through direct and indirect lobbying efforts. The DMCA didn't just spontaneously appear out of thin air. There must be action-for-action retaliation.