Relevant - https://news.ycombinator.com/item?id=18342042\ JPEG image of Shakespeare which is also a zip file containing his complete works
no such item
Remove the trailing backslash.
YouTube-dl source code encoded in two images
11–20 of 110 posts
Re: YouTube-dl source code encoded in two images
#12We should start a political movement to stop this tyranny. Like the climate change movement it will take time but at least we will make some progress.
Re: YouTube-dl source code encoded in two images
#13Great, now Imagemagick will receive a DMCA takedown notice! Can someone encode Imagemagick as audio using sox?
Re: YouTube-dl source code encoded in two images
#14Genuine 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 :/
Re: YouTube-dl source code encoded in two images
#15Genuine 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 :/
Then it’s no longer open-source projects.
Re: YouTube-dl source code encoded in two images
#16Distributing the code is not an issue. It’s keeping development moving when YouTube changes their apis.
This is also an interesting case for github. youtube-dl is popular enough that this just
might annoy enough people to find an alternative way to collaborate on it. Meanwhile github becomes “that platform that might kill you project”
Re: YouTube-dl source code encoded in two images
#17Genuine 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 :/
Sounds like what you are looking for is closed source software where you get to dictate precisely who your licensees are and under what specific terms they must use your software.
This is a model I have started to seriously consider due to increasingly prolific IP theft concerns. There is software that is so capable that it could be considered a weapons platform from some perspectives. I really worry about this stuff in context of China/Russia/India/et.al. and our willingness to relinquish our various competitive advantages.
Re: YouTube-dl source code encoded in two images
#18Genuine 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 :/
Then it’s no longer open-source projects.
That's why I'm curious, it's more of a movement I guess, also there are multiple types license and idk if blacklisting a specific entity is possible or if it has any legal grounds
Re: YouTube-dl source code encoded in two images
#19This recent takedown will only make more people know about YouTube-Dl and hopefully create more forks. When will these big companies learn!?
The takedown may spark new life to the project development, which severely slowed down in the last months because there are too few maintainers.
Re: YouTube-dl source code encoded in two images
#20Genuine 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 :/
Maybe we need apache with DMCA clause (like patent clause)-if you ever invoke DMCA your license is forfeit?
I'm not sure how viable it is - the GPL is hack on top of copyright - but the DMCA is an extension on top of copyright too (however ill advised).