Yellow-Dog-Man
Add the abilitytouse cookies.txt as an argument for YouTube DL for any Firefox/chromium Based browser
Is your feature request related to a problem? Please describe.
While Firefox and chromium are options they're open source meaning that they're open to forks Resonite cannot possibly support all these forks so it'd be nice if we could have cookies.txt as an argument For You Tube DL
Describe the solution you'd like
I want youtube DL to use cookies.Txt when it's in the runtime data folder
Describe alternatives you've considered
None
Additional Context
Youtube recently completely broke Youtube videos for me as it requires a login to view video content
Requesters
@epicEaston197
This should already be supported?
Under Settings -> Networking -> Use Cookies From Browser
Does that not work for you?
This should already be supported?
Under Settings -> Networking -> Use Cookies From Browser
Does that not work for you?
I use LibreWolf which is not a supported option
To explain, if you're using a browser that isn't supported by either the enum to select the browser or the yt-dlp --use-cookies-from-browser, it would be great if you could use exported browser cookies to watch videos fetched from yt-dlp.
Exported browser cookies from most browsers are exported in the same format. This would make it so you wouldn't have to add more browsers than the sane ones to the list, and allow people who use unsupported browsers to use the --cookie FILE flag in yt-dlp to achieve the same result
They want to specifically use the "--cookies" flag that lets you provide a Netscape Cookie file. The --cookies-from-browser flag only searches the profile locations of the standard official versions of each browser.
Trying to search %appdata%\mozilla\firefox doesn't do much when your profile is actually in %appdata%\waterfox\profiles\
example from me: i use marble, a fork of firefox, it just adds native titlebar support (i like my windows aero effect :3)
Oh, so this would essentially be providing a path to the file instead? That can be added then, thanks!
For the "Netscape Cookie file" is this the only format supported for that option? Do most browsers use that file type?
At least for Firefox it exports Depending on the website www.youtube.com_cookies.txt I don't know what followed for him at this is cause it appears to just be a Text file
For the "Netscape Cookie file" is this the only format supported for that option? Do most browsers use that file type?
It is the format that ytdlp uses, and it's standard; but it does require a specific export format.
https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp
Looks like you can also tell it where "Chrome" is, so that might be another option for a custom path.
In case you install Chrome using Flatpak, the config is located in ~/.var/app/com.google.Chrome. To pass the cookies from this location use --cookies-from-browser chrome:~/.var/app/com.google.Chrome/
Looks like you can also tell it where "Chrome" is, so that might be another option for a custom path.
I would like to be able to just set an arbitrary path for example there would be a text field or something that I could just put this into
C:\programs\Steam\steamapps\common\Resonite\RuntimeData\www.youtube.com_cookies.txt
Looks like you can also tell it where "Chrome" is, so that might be another option for a custom path.
Not sure if this would work with a couple of use cases:
- Privacy focused browsers which periodically delete cookies. Exporting them instead of providing custom browser location would be the only option in this case
- Using a more custom browser, such as Ladybird, which uses a custom browser engine, would not work with any of the cookies from browser option, and would need to be exported. (While my specific example doesn't currently support cookie export, there could be one out there (lynx maybe?) that allows cookie export, but not compatible with the browser option)
I would like to be able to just set an arbitrary path.
I understand, but:
Based on my reading, the cookie file can sometimes need to manually generated and updated and synced etc. So if the other one can fetch it automaticaly from browsers when it knows where they are, that might be a more automatic thing.
Yeah, supporting both would also be useful for handling portable installs or proton/linux support since those would be normal browsers but in an unusual location.
So apparently this isn't a blanket ban youtube is apparently flagging users IPs who use youtubeDL
Wait I'm not getting blocked anymore?
Maybe I hit like some form of "limit"
And I can only load a certain amount of videos before it thinks I'm a bot downloading videos?
So if you're in a session with people importing youtube videos a lot you might hit this "limit" and not be able to load youtube videos anymore
Until this arbitrary time expires then you'll be able to watch more youtube videos
This is just my guess