Live data from Hacker News

YouTube-dl source code encoded in two images

twitter.com

61–70 of 110 posts

Re: YouTube-dl source code encoded in two images

#63
Just for fun, I wrote a little Python script to convert the image files back into the original archive.

Use 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

#64
post #4

This recent takedown will only make more people know about YouTube-Dl and hopefully create more forks. When will these big companies learn!?

Plenty of people used and knew about youtube-dl already. It's made the front page of HN multiple times [0]. I've used it as a key example of why/how non-programmers should learn to use the command-line. People who weren't already aware or didn't care to learn aren't going to be significantly moved now.

[0] https://hn.algolia.com/?q=youtube-dl

Re: YouTube-dl source code encoded in two images

#67

Side Question : Is there a distributed alternative to github ?

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.

Re: YouTube-dl source code encoded in two images

#68
post #67

Earlier 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.

Gitlab is working on federation, or they at least have an open issue about it.[1]

Meanwhile there is a federated git as a reference implementation called Forgefed.[2]

1. https://gitlab.com/gitlab-org/gitlab/-/issues/6468

2. https://forgefed.peers.community/

Re: YouTube-dl source code encoded in two images

#69
post #14

Genuine 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.

Politics is just getting what you want.

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.

Post reply on HN