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
So I updated to the latest version 1.27.0 this week and tried to download a bunch of Twitter accounts again with the same config from roughly 5 months ago.
After hitting the rate limit a few times, Twitter forcibly logged me out everywhere and I got the known 401 Unauthorized (Could not authenticate you) error cause I was only using browser cookies to log in.
This I was able to work around by logging back into my account and adding my username and password to the config for the relogin option to work.
However after getting forcibly logged out again and using the gallery-dl relogin a few times, my account was temporarily locked and I had to do the Arkose challenge.
I then cleared cache for twitter and added a delay with "sleep": 1, "sleep-request": 1, which was enough to prevent ever hitting rate limit, but I was still eventually logged out, and after triggering the relogin multiple times my account was suspended for trying to evade suspension.
I just got my account unlocked and I still want to download everything I can, but want to avoid having any further troubles. What settings can/should I use to prevent getting forcibly logged out and then suspended?
I saw the comments in #5532 saying that upping sleep and sleep-request to 2 seconds is enough, but how reliable is that?
Also, could a Premium subscription increase the rate limit at all?
For reference here's my current config that got my account suspended:
I wrote something short like
"Hi, I seem to have been mistakenly suspended cause of an issue with a browser addon that was constantly logging in and out of my account. I thought the emails notifying me of a new login were an error and didn't react in time. I've removed the addon now so it shouldn't happen again. Please unlock the account. Thank you."
I wrote something similar when I got banned months ago, never got a reply back. It seems like Twitter is doing collateral punishment by banning every single person for "ban evasion" after getting rate limited and sharing the same IP address as a banned user because I haven't gotten banned after getting rate limited while using a residential IP address.
So I updated to the latest version 1.27.0 this week and tried to download a bunch of Twitter accounts again with the same config from roughly 5 months ago.
After hitting the rate limit a few times, Twitter forcibly logged me out everywhere and I got the known
401 Unauthorized (Could not authenticate you)
error cause I was only using browser cookies to log in.This I was able to work around by logging back into my account and adding my username and password to the config for the
relogin
option to work.However after getting forcibly logged out again and using the gallery-dl relogin a few times, my account was temporarily locked and I had to do the Arkose challenge.
I then cleared cache for twitter and added a delay with
"sleep": 1, "sleep-request": 1,
which was enough to prevent ever hitting rate limit, but I was still eventually logged out, and after triggering the relogin multiple times my account was suspended for trying to evade suspension.I just got my account unlocked and I still want to download everything I can, but want to avoid having any further troubles.
What settings can/should I use to prevent getting forcibly logged out and then suspended?
I saw the comments in #5532 saying that upping
sleep
andsleep-request
to 2 seconds is enough, but how reliable is that?Also, could a Premium subscription increase the rate limit at all?
For reference here's my current config that got my account suspended:
The text was updated successfully, but these errors were encountered: