-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://yt-dl.org/ broken by a German court #32495
Comments
This is true though not what "broken site support" was intended to mean. There's no point downloading that version anyway: the court is actually doing you a favour. When a new release is made the DNS will have been reset to avoid this block. Meanwhile, refer to #30839 for the nightly build that fixes many known issues. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
I'm sorry, as you may not like to hear this, but if "There's no point downloading that version", which happens to be the latest release, that's a strong indicator that there should have been a new release since. It's up to you as maintainers, though. While the list of known issues now fixed seem worthy, there may be good reasons not to have cut a release yet. Anyway, I didn't want my main point to be whether there should be a release or not. I wanted to ask: How are we expected to know the latest version?
(which I admit perhaps was not the proper way before, either), but now that obviously fails with a 403 error. Thank you very much for this software. It's dismaying that it is now having this kind of issues again. |
If you really want that version you find the binaries on the github releases page: https://github.com/ytdl-org/youtube-dl/releases/latest |
Even if a version was released with all site extractors passing their tests, the turnover of site issues would invalidate the release after a few days. For now, the nightly release is the best bet. Should some site work with 2021.12.07 and not with the latest nightly build, please open a new issue. A lot of data about available versions is returned as JSON from https://api.github.com/repos/ytdl-org/youtube-dl/releases/latest. For convenience, the nightly builds are released in a different repo and the internal update check uses the corresponding JSON URL ( |
Also you can just add to cron something like
and the nightly build will update itself |
This comment was marked as outdated.
This comment was marked as outdated.
The last version can be build with
But this does not solve the problem that a player must be downloaded from https://yt-dl.org/ Example:
Is it possible to add the needed player here at github? |
Censoring as "favour" is a nice idea. ;-) A traceroute shows
The IP is blocked by this company: Professional censoring in GERMANY! |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I am in Central Europe (not in Germany) and the site is blocked in our country: This is the first time I see this kind of censorship... Description/README on GitHub has instructions to use that site, but it doesn't work (because the site is blocked):
|
Until the domain points to a valid domain, a version of the README that doesn't mention yt-dl.org is provided in the PR above. |
BTW it properly responds with: I like that! 😄 |
Checklist
Verbose log
Logs not relevant
Description
When attempting to download
youtube-dl
as described inREADME.md
orREADME.txt
, you get a "403 forbidden" error. Visiting that website gives this message:Access denied
Due to a ruling of the Hamburg Regional Court, access to this website is blocked.
Zugriff gesperrt
Aufgrund eines Urteils des Landgerichts Hamburg ist der Zugriff auf diese Website gesperrt
The text was updated successfully, but these errors were encountered: