Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Youtube-dlc – Download videos from YouTube or other video platforms

github.com

Post reply on HN
Print view View original

101–109 of 109 posts

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#101

Post by theidel »

brailsafe wrote: post #42

Seems like this is derived from a dissatisfaction with maintenance, but all I'm seeing is that they're maintaining things just fine. Yes, there are a lot of open PRs, but there are also quite a few merged, reviewed, and closed PRs. While I do support forks in the spirit of FOSS, I disagree that YT-dl is being poorly maintained and find that it continues to work well for my needs. To the person who started the fork, w…

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.

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#102

Post by theidel »

dewey wrote: post #12

YouTube-dl as a name is already confusing enough because it works for so many sites and YouTube is just one of them. Why complicate it even further in your fork by renaming it to YouTube-dlc (The "c" stands for community I guess) when dlc already stands for so many other things.

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.

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#103

Post by theidel »

dannyw wrote: post #25

Fantastic. This is the beauty of open source. `youtube-dl` has had quite a number of breaking issues, where fully working PRs were raised and tested but not merged for weeks and with no communication. I am glad to see `youtube-dlc`. Please, support the self updater as well (if it is not supported already). For my archival servers, I have a cron job that updates every day, I hope I can do that with youtube-dlc too.

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.

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#104

Post by theidel »

hombre_fatal wrote: post #83
masklinn wrote: post #64

Earlier quoted context omitted.

> It makes sense that it's easier to give ydl has 700 open PRs, not 25k+. ydl hasn't had 25k+ PRs in its lifetime either, it's had 4k: GH issues and PRs are the same object, so the sequence is shared.

Doesn't change the point. All of the fork's 55 PRs except 2 and most of the issues were made by the forker himself as well. It's not like the forker inherited all the open issues/PRs, they just dropped them all. Getting popular and having the masses leave a bunch of issues/PRs is hard. Reviewing code is hard and takes more expertise than writing it. A lot harder than reviewing your own PRs on a motivated (for now) fo…

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

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#105

Post by theidel »

OzzyB wrote: post #91
claudeganon wrote: post #72

Earlier quoted context omitted.

It’s odd to me how nontechnical people have migrated to GitHub to make bug reports on software they use. The other day, I was trying to use a Python library to scrape some stuff. It kept breaking. I looked on the issues page and there were many, essentially useless bug reports asking them to fix the issue. I opened up the script and changed about 7 lines and it worked fine.

I've noticed this trend too -- but I've also noticed people starting GitHub Repos for websites/apps just for the Issues. No code, no PRs, just a way for the public to create Issues. Not sure what this means for the "culture of code" other than things are blurring...

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.

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#106

Post by noxer »

ldarby wrote: post #49
noxer wrote: post #43

One tool that does everything. Its literally backwards. It eventually always results in one tool that's constantly broken. There should be a tool for each site if there is a maintainer who actually cares about that site.

This is misapplying the unix philosophy. There would be too much duplicated functionality between different tools for different sites. It would be like having different versions of /bin/ls for different file systems.

"too much duplicated functionality" What should that be? Who decides when its too much anyway? No one cares about duplicated functionality in stuff they don't use. Probably 90% only want to download form YouTube. So why would they care if part of the code is used in another downloaders they don't use. If you create a kernel/OS/Distro sure you don't want duplicated functions but this is just a downloader tool. Also if there are generic functions that can be used by different tools you create a lib. No one has to reinvent the wheel. Would it cause more work if summed up? Yes most likely but the work is shared and independent.

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#107

Post by yencabulator »

pfranz wrote: post #95
u801e wrote: post #71

Earlier quoted context omitted.

I don't think that editing comments that you didn't make should ever be a feature. This is something that could easily be abused to make it appear that someone else said something they didn't actually way.

I can see what you're saying in principle, but what if a bug is opened with "this stopped working for me" but evolves into a very specific issue? Should the maintainer open a new bug, link to it and close the old one? In practice, I find it really useful to tidy up the top message of a bug report (but /really/ like seeing history of it). I also see cases where users spam raw logs into updates and tidying it up (perha…

Then there should be a "non-message" textfield up top, that doesn't pretend it's the original report, or forge its author.

Re: Youtube-dlc – Download videos from YouTube or other video platforms

#108

Post by account42 »

theidel wrote: post #102
dewey wrote: post #12

YouTube-dl as a name is already confusing enough because it works for so many sites and YouTube is just one of them. Why complicate it even further in your fork by renaming it to YouTube-dlc (The "c" stands for community I guess) when dlc already stands for so many other things.

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.

The name makes it seem more like you are attempting a hostile takeover of the project branding. Definitely not a great way to go about this.
Post reply on HN