HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ytdl-org
youtube-dl
Python2012–2026
ytdl-org / youtube-dl

youtube-dl

Command-line program to download videos from YouTube.com and other video sites

188Distinct people
220Mentions
2Explicit recommenders
141.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Command-line program to download videos from YouTube.com and other video sites

GitHub

Where it is used

  • youtube-dl-api-server — youtube-dl-api-server uses youtube-dl to power a REST API that retrieves video information from various sites. Source

What people are saying

Here's a couple (albeit macOS focused) favorites of mine: - Deliveries: macOS / iOS package tracking https://itunes.apple.com/us/app/deliveries-a-package-tracker... -…

firloop used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:20:21 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year220 dated mentions

Observed mentions: 2012-03-11 07:35:07 UTC to 2026-09-26 00:27:46 UTC.

020402012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 21 mentions; 1 submissions, 20 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 51 mentions; 3 submissions, 48 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 37 mentions; 5 submissions, 32 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 19 mentions; 2 submissions, 17 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC12111
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC13112
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1019
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC1129
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC21120
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC13211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC51348
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC37532
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC17215
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC19217
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC808
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

37 sources
Not only have the yt-dl maintainers had to deal with the legal issues and the stress that comes with it, it appears they have a massive spam problem on GitHub which must make it difficult to efficiently deal with bugs. I was looking through the reported Issues recently due to a bug that caused yt-dl to stop working for a few days; a PR was quickly written to address the issue but it wasn't merged for several days. That's when I saw Issues like this: https://github.com/ytdl-org/youtube-dl/issues/29809
In Move myself to inactive
Seems to be https://github.com/ytdl-org/youtube-dl/pull/24604? The complaint is that it's come up repeatedly ('Not again. Use search') - agree it's a bit of a brush off, and it's not helpful for anybody (perhaps most of all the maintainers themselves!) that it doesn't link any of the others, or the one that was merged, or the first one with a better explanation for rejection, or whatever. Something I would say though (that as above doesn't seem to be the issue, but who knows maybe it contributed) is that you could put a bit more time into the PR description & title. There's little human-readable (without following a link) information in the title. Your checked boxes are all broken (`[x ]` & `[ x]`) despite the instructions on how to do it (`[x]`) that you've left in (that also indicates a bad template in fairness, should be a comment (`<!
Read the rest
--`) so only you see it, while editing). It's hard to read, separating your own description from the templated instructions. You also didn't follow up on it in a way that seems like you're bothered, nor at all for several months. When you open a PR like this you're being helpful and fixing something yes, but you're also asking someone to maintain it for you going forward, and really you just proved that you wouldn't have anything further to do with it. Maybe if you'd followed up when it was closed asking for a link to where it had been addressed previously so that you could help test it ('since it is still not working for me with the latest released version or master @ deadb33f') it would have gone differently, perhaps the maintainer simply misunderstood what you were fixing, and would've reopened it.
In YouTube-dl's first release since June 2021
https://github.com/ytdl-org/youtube-dl/pull/29989 There's this pull request that works on fixing the problem (not merged yet), I don't know if it is yours under a different alias, but you can see the work and edge cases involved for something that a priori seems simple ("just truncate the name!" haha). Also the dude making the PR looks like an external contributor. It seems like normal polite open source interaction there to me, despite what could be perceived as a negative initial reaction. What might come across as dry or brushing off could be genuine concern at unforeseen consequences.
In YouTube-dl's first release since June 2021
For a long time now for me youtube-dl downloads YouTube videos at 50kb/s, which makes it impractical to use in conjunction with mpv. I need to leave youtube-dl running in the background for several hours to then watch the video in mpv. Now from the comments I've found out about yt-dlp[1] which claims to fix this issue[2]. Will check it out. [1]: <https://github.com/yt-dlp/yt-dlp> [2]: <https://github.com/ytdl-org/youtube-dl/issues/29326>
In YouTube-dl's first release since June 2021
> With the removal of dislike stats from the YouTube API, our backend will switch to using a combination of scraped dislike stats, estimates extrapolated from extension user data and estimates based on view\like ratios. In case anyone is wondering, the extension seems to calculate the dislike count from the average rating, which is something that the YouTube API still returns. The average rating is calculated as follows [1]: (like * 5) + (dislike) ---------------------- * 5 (like + dislike) * 5 If you do some algebra, the dislike count is calculated as (likes * (5 - rating)) / (rating - 1), which is what the author uses in their code [2]. I'm not sure what they mean by using "a combination of scraped dislike stats, estimates extrapolated from extension user data, and estimates based on view\like ratios" because I don't see them explicitl
Read the rest
y using anything like that in their code. Maybe it's something for the future. Hopefully someone can clarify what they mean by this statement. [1] https://github.com/ytdl-org/youtube-dl/issues/29663#issuecom... [2] https://github.com/Anarios/return-youtube-dislike
In Return YouTube Dislike - Extension
I'm very, very sorry to say that IMO he has a point about toxic community. https://github.com/ytdl-org/youtube-dl/issues an example: Rich with people who demand a lot, pay nothing and do nothing. FWIW, I once stood next to someone at a conference while he was explaining what an evil person I was. He didn't recognise me, but he felt able to talk with confidence about why I wrote the code I'd written and why it was licensed as it was. It was really sad.
In [dead]

Showing the 15 most recent of 37 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.