-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Question] Questions about youtube-trusted-session-generator #11
Comments
Headless doesn't work: #2
That's what the Docker version do: https://github.com/iv-org/youtube-trusted-session-generator/blob/master/docker/scripts/startup.sh
We don't know either, theoretically it should be valid for long time. So if you are rotating it just do it like every hour. That's why we said:
|
Thanks. Sorry, didn't notice the tool had a Dockerfile. I said nothing about using Chromium headless mode, didn't even consider using it. As for token rotation, I will setup my tool to run once a day, hopefully that will be enough. |
Is your enhancement request related to a problem? Please describe.
Issue #4947
Describe the solution you'd like
You have added documentation on how to enable usage of the web client with session keys to Invidious installation instructions. Your solution works well, however, the documentation could use an improvement. For example, there's no mention that youtube-trusted-session-generator session generator tool requires a working X server and Chromium/Chrome browser installed. And no workarounds are provided for running the tool headlessly.
Since the session generator tool requires no user interaction, there's a simple workaround which would enable the session generator to run on headless systems:
install and run an Xvfb server (I run it as a systemd service, but simple shell backgrounding will work too) and set the DISPLAY variable to it's display before running the session generator tool.
One more thing would be useful is to know approximately how often does one need to rotate the session keys.
I wrote an automated tool for my own internal use but not sure how often I should run it.
The text was updated successfully, but these errors were encountered: