Replies: 14 comments 8 replies
-
the people you read are wrong use cookies |
Beta Was this translation helpful? Give feedback.
-
the yt-dlp contributors said never use cookies youll get cookie banned
…On Tue, Aug 13, 2024, 8:11 PM Paul Henning ***@***.***> wrote:
the people you read are wrong use cookies
—
Reply to this email directly, view it on GitHub
<#330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFY3LT54MWH2HYFNROATEULZRI45JAVCNFSM6AAAAABMOUCFQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZSHA3TEOI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
It's in your venv. |
Beta Was this translation helpful? Give feedback.
-
sorry to bother, but i don't understand this. when i used yt-dlp (after adding a yt-dlp config file to bypass the "confirm you're not a bot...") to download a video, it worked fine, but when i used Tubeup, yt-dlp shows the bot error again. as you can see, i am working in the venv so im using the yt-dlp that is with tubeup. does tubeup somehow make yt-dlp not load the yt-dlp config file that i added? |
Beta Was this translation helpful? Give feedback.
-
i guess this is similar to what i want #196 (comment) |
Beta Was this translation helpful? Give feedback.
-
no we're not having open flags it invites abuse. no I do not care about your specific use case. Use a cookie, if it's banned get another, go slower. Use sleeps. You can either use the sleep command in Linux or use the built in sleeps function. You need to change how you behave to not appear like a scraper. Again, open yt-dlp args will not fix this and cause a nightmare for the site. It's not happening. Edit: I do not care one lick what the "top contributor" to yt-dlp says. I've pumped 300k videos into IA. The sleeps function is in yt-dlp because of me. Listen to me. Get a cookie or figure out how to edit the config in your yt-dlp instance to force oauth. |
Beta Was this translation helpful? Give feedback.
-
And if you're getting the bot warning you've gotten your IP flagged, which no amount of open yt-dlp args will fix,. Wait 72 hours before ripping another video. |
Beta Was this translation helpful? Give feedback.
-
also do you have yt-dlp installed elsewhere? where does your path point for yt-dlp? edit: Have you tried moving the config to home aka |
Beta Was this translation helpful? Give feedback.
-
using cookies only worked for the first video . the commands after that, output gave the same bot error |
Beta Was this translation helpful? Give feedback.
-
tried to pull newer cookies, it only worked for 3 commands. might be too hard for me, but i'll try adding netrc args to the tubeup.py file as there is another way to authenticate using netrc |
Beta Was this translation helpful? Give feedback.
-
Thats not gonna work with .netrc. Are you using sleeps?
Go slower. Stop looking like a bot to Youtube and sucking everything down as fast as you can with one bare Tubeup command pointed at a channel. Have yt-dlp print out a channels URLs into a batch file, then make batch file with the sleeps and cookies.
Use Vim to mass edit the file and have it sleep 90 seconds tops per video. You also need to wait 72 hours at least once you start getting those IP bans before Youtube stops blacklisting you. Edit: Are you using a VPS to rip that does nothing but rip, or are you using the same machine and IP bound to a machine you watch Youtube on? Thats another way to avoid scrape bans is to look like legitimate watching activity. If you read the front page, it says channel rips aren't recommended. Well we've all been living on borrowed time, and sadly not even your vaunted oauth command - and I do not care what yt-dlp does alone outside of tubeup post azll the screenshots you want - will fix this. Go slower. Wait longer between bans at least 72 hours. Use a cookies and update them often. Rip a channel a video at a time if you have to all of these things have been working for me. |
Beta Was this translation helpful? Give feedback.
-
i used the VPS to upload some videos back in June. i had no problems then.
after i was done i never used the VPS untill the day i contacted you, when
i discovered my ip was blacklisted (from the very first tubeup command).
so, i know waiting for 3 days is not going to work for my case (because i
stopped for 2 months before i did it again).
i do have a batch file , each line is a tubeup command , but i dont use
sleeps because it takes around an hour to upload one video to ia. how is a
90 second sleep going to help? the time the tubeup command takes to upload
its video should serve as a sleep until the next tubeup command, no?
anyways, thanks for your help
…On Tue, Aug 20, 2024, 1:18 AM Paul Henning ***@***.***> wrote:
Thats not gonna work with .netrc. Are you using sleeps?
sleep $((RANDOM % 90)) ; tubeup
Go slower. Stop looking like a bot to Youtube and sucking everything down
as fast as you can with one bare Tubeup command pointed at a channel. Have
yt-dlp print out a channels URLs into a batch file, then make batch file
with the sleeps and cookies.
yt-dlp --get-id [CHANNEL] > batch.sh
Use Vim to mass edit the file and have it sleep 90 seconds tops per video.
You also need to wait 72 hours at least once you start getting those IP
bans before Youtube stops blacklisting you.
If you read the front page, it says channel rips aren't recommended. Well
we've all been living on borrowed time, and sadly not even your vaunted
oauth command - and I do not care what yt-dlp does alone outside of tubeup
post azll the screenshots you want - will fix this.
Go slower. Wait longer between bans at least 72 hours. Use a cookies and
update them often. Rip a channel a video at a time if you have to all of
these things have been working for me.
—
Reply to this email directly, view it on GitHub
<#330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFY3LT6YAWWISXBBL3GQ5DDZSJVMPAVCNFSM6AAAAABMOUCFQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZYHEYDQMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
thanks
…On Tue, Aug 20, 2024, 4:17 AM Paul Henning ***@***.***> wrote:
and on that oauth plugin, remove yt-dlp from tubeup venv, reinstall the
latest nightly in it's own venv, try to see if tubeup can see the seperate
venv, then inject that oauth thing and see if that allows it to work, if it
works we'll update README unless theres other code changes needed, if thats
the case do a PR with a flag for oauth and we'll merge it.
—
Reply to this email directly, view it on GitHub
<#330 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFY3LT2M5AIRGXWBZBNH4CLZSKKKRAVCNFSM6AAAAABMOUCFQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZYHE4DSMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
solved. see PR |
Beta Was this translation helpful? Give feedback.
-
people say if you see this error it means Youtube banned my IP.
However, i know the solution to this issue.
by using Oauth plugin and injecting it into yt-dlp it should solve it. this is the git page: https://github.com/coletdjnz/yt-dlp-youtube-oauth2
My question is: where is the config file for yt-dlp? i dont know where to find it. i used pipx to install Tubeup.
i tested the Oauth plugin on a yt-dlp other than the one that Tubeup works with and it worked. now i just need to do it with the yt-dlp that Tubeup is working wih
Beta Was this translation helpful? Give feedback.
All reactions