3 ms·
There's no need to keep that code in the main yt-dl codebase if it is for special cases. You could imagine a siloed yt-dl plugin called crack-riaa with separat
by tantalor 6y ago
There's no need to keep that code in the main yt-dl codebase if it is for special cases.
You could imagine a siloed yt-dl plugin called crack-riaa with separate tests, hosting, etc.
If yt-dl detects the obfuscation, it could fail with an error message point to the plugin's documentation.
- remram 6y agoThat would only move the problem. That plugin would still need a Git repository, an issue tracker, tests, and an update mechanism. Or are you trying to say you don't care if this specific part of yt-dl gets deleted from the internet by RIAA?
- tantalor 6y agoIt decouples the thorny part of yt-dl from the mainline and reduces risk of complaints in the future. I do care if this part gets deleted, that's why I think it should be hosted somewhere more reliable than GitHub. There are other options which aren't as polished, but may be better for hosting risky code like this, including self hosting. This code needs to be underground.