theidel

True. But as long as it's widevine you can remove DRM. So some hope. Nothing is safe. It is just a matter of time when something will be cracked.

At least there is a feature called 'discussions' coming soon to github. That should hopefully minimize the abuse of issues. But that is also due to the fact of current github. Not everyone is displaying their email and there is no other communication channel.

Actually I merged quite some PRs that were open or even closed. However I tested and reviewed all I can but those geoblocked ones. But most of these were verified already or I could use some simple self hosted vpn. But do note that my reviews are not really in line with the strict coding conventions originating from the main project. As long as it works and isn't totally gibberish it will be approved by me. I rather want functionality and somewhat stability quite fast.

Although totally agree reviewing can be such a pain..

Yes that is exact one of the reasons why I created this fork. The self updater should hopefully work in a future release. To be honest I haven't dealt with that yet. But feel free to open an issue so it's on my TODO-list.

I agree. Tho my main intention was backwards compatibility so that changes can easily be merged back into main project. There are also lots of people using it in their python projects. The naming discussion comes up every now and then as an issue. So for now I would like the name youtube-dlc to stay. But depending on how things go in the future I may change the name.

I wrote an email to all three core maintainers (one of them even twice) and to some of the inactive maintainers. There was no reply at all. However one reacted on github where I addressed the maintaining issues but basically just ignored it and all those who had similar concerns.

Well I am not the only one being frustrated about how things go. Especially the lack of communication. It's basically non-existent. At least the PRs that are merged are mostly either adult related or youtube. If your site is not even known to the maintainer - good luck. That will never be merged tho it may be one of the biggest sites in asia or so.

I second that. But yes you are right it's my fault that I haven't done that already. Be assured that I will include some information regarding what you said in the readme.

Nope. Maybe there is someone with a fix which can be merged. So far most people filter formats to their needs but that's not an option for basic users I guess..

Yes it's stressing and time demanding. But you are absolutely right about how the maintainers treat other people. At least it is open source. There are quite some closed-source projects that ran into troubles and basically disappeared. I am not sure how they will react since the fork gained some attention now. However it's not my intention to let them look bad in any kind or act like I am better. All I want is a working solution where contributions by the community are acknowledged. But my attempt to openly point that out (issue youtube-dl dying?) basically got ignored and closed.

there are actually quite a few that uses youtube-dl. So far I don't know if anyone uses youtube-dlc. But I already got two messages that they want to build a webapp/service using youtube-dlc.

Yes that is a good point. The architecture is not fully suited to the current situation. There is actually already a base structure so it would only need the plugin system which pulls the missing extractors/downloader on the fly. Tho I may see problems here when it comes to windows binaries.

Another advantage would be to easier maintain those extractors as well as all issues that arise around specific ones. So no more thousands of issues addressing different extractors in one project.

This is something I was going to address but wasn't my main focus in the beginning. But I made another write-up on reddit https://www.reddit.com/r/DataHoarder/comments/ir8ic6/youtube...

A tiny conversation about this here as well https://github.com/blackjack4494/youtube-dlc/issues/56#issue...