You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For the initial authentication, I'd like to be able to just provide the cookies right away, not deal with the interactive login or 2FA in the CLI.
Especially with the docker-compose setup, it's a bit bothersome.
Describe the solution you'd like
I'd like if users could either:
Perform document.cookie on Twitch and paste that string either in a file, run.py, or as an environment variable which can be set in the docker-compose.yml file.
To use an extension like cookies.txt to export the cookies to a text file, and put that in the cookies/ directory for the miner to use. (Netscape HTTP cookie file)
A cookie string via document.cookie is easy enough to parse manually.
Netscape HTTP cookie files can be parsed by http.cookiejar.
Even better if both could be supported, as non-technical users will probably have an easier time with the extension. (youtube-dl recommends it iirc)
Meanwhile, for technical users, just doing document.cookie is a lot faster than any other means of getting cookies or setting the miner up.
This way the miner can work with no interaction on the first run, making it a much more pleasant experience to set up.
Describe alternatives you've considered
N/A
Though it could be nice to add the docs for that for Docker Compose, users have to do the docker-compose run --rm miner first to get through authentication if they have 2FA enabled before they can just run docker-compose up -d normally.
What do you think?
Maybe next week I could see if I have time to contribute this, at least with the cookie string.
Also thanks for merging the Docker support! I only just noticed that's a thing today! ^-^'
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For the initial authentication, I'd like to be able to just provide the cookies right away, not deal with the interactive login or 2FA in the CLI.
Especially with the docker-compose setup, it's a bit bothersome.
Describe the solution you'd like
I'd like if users could either:
document.cookie
on Twitch and paste that string either in a file,run.py
, or as an environment variable which can be set in thedocker-compose.yml
file.cookies/
directory for the miner to use. (Netscape HTTP cookie file)A cookie string via
document.cookie
is easy enough to parse manually.Netscape HTTP cookie files can be parsed by
http.cookiejar
.Even better if both could be supported, as non-technical users will probably have an easier time with the extension. (youtube-dl recommends it iirc)
Meanwhile, for technical users, just doing
document.cookie
is a lot faster than any other means of getting cookies or setting the miner up.This way the miner can work with no interaction on the first run, making it a much more pleasant experience to set up.
Describe alternatives you've considered
N/A
Though it could be nice to add the docs for that for Docker Compose, users have to do the
docker-compose run --rm miner
first to get through authentication if they have 2FA enabled before they can just rundocker-compose up -d
normally.What do you think?
Maybe next week I could see if I have time to contribute this, at least with the cookie string.
Also thanks for merging the Docker support! I only just noticed that's a thing today! ^-^'
The text was updated successfully, but these errors were encountered: