Am I the only one getting "This video is unavailable." on all youtube videos? 'Cause I am!
Anyway, another curious discovery: if you rely on youtube-dl for your youtube needs while using invidious instances to hide your ass, be aware that youtube extractor (which WILL be used for those links, well, the ones recognized by the extractor anyway) is hardcoded to download webpages from youtube.com. I kid you not, it's true. Not that it's a major risk if you're using Tor with ytdl anyway, just FYI.
>Am I the only one getting "This video is unavailable." on all youtube videos?
*Am I the only one getting "This video is unavailable." on all youtube videos with youtube-dl?
$ torsocks -i youtube-dl <some shit>
ERROR: no conn, hlsvp, hlsManifestUrl or url_encoded_fmt_stream_map information found in video info; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type youtube-dl -U to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
$ torsocks -i youtube-dl -U
Updating to version 2019.09.01 ...
ERROR: unable to download latest version
Had a problem with youtube-dl today and it worked after upgrading to version 2019.09.12. NewPipe is broken but they usually take about a day to fix the youtube change.
>>6664 Wow thanks for telling me about the youtube extractor. Just checked the source code and you're right invidious comes under the youtube extractor. Guess I'll download videos through the invidious instances from now on.
>>6669 >torsocks
Youtube-dl has socks5 support (more specifically, urllib):
$ youtube-dl --proxy socks5://127.0.0.1:9050
Note that ffmpeg doesn't support proxy. So you need to force HLS download to "native" (see --hls-prefer-native). Also, change your user agent:
--user-agent "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
>>6665 >with youtube-dl
Not sure this is youtube-dl specific issue. Other people are telling me videos are unavailable. AFAIK, only music companies on Germany and Japan were doing this, but now it seems other countries are doing that too ("geoblocking").
>>6680 What I was talking about is whenever you use youtube extractor (indicated by [youtube] in the beginning of some lines) it's going to load stuff from youtube.com, regardless of an actual URL you provide. Of course, proxying would still work normally.
>user agent
Actually, the new youtube-dl has been having randomized chrome-like user agent for a while now. The dump-user-agent option hints at that.
>Not sure this is youtube-dl specific issue.
I'm pretty sure it was. Just some random minor change in that JS/HTML interface could knock out the script. Not that it didn't happen before. It did.
This seems to be the commit to "fix the extraction".
https://github.com/ytdl-org/youtube-dl/commit/bf1317d257d13188601c837c983830355c6203e5
It's far from trivial, as you can see. Gomblexidy LOL
I keep having to Ctrl+U news sites then search the source for the m3u8 file (or whatever it's called) and then pointing youtube-dl at that. Sucks that I can't just right-click and save the damn video.
Anyway, another curious discovery: if you rely on youtube-dl for your youtube needs while using invidious instances to hide your ass, be aware that youtube extractor (which WILL be used for those links, well, the ones recognized by the extractor anyway) is hardcoded to download webpages from youtube.com. I kid you not, it's true. Not that it's a major risk if you're using Tor with ytdl anyway, just FYI.
Thanks for your support.