[Twitter] Login rejected as suspicious

[Nicosow2]

I used to use the method of putting your password and username in the config file, it was the best because it was the most practical, but since yesterday when I went to download images from an artist with a lot of posts it started to give this error, I wouldn't even comment here about this error if the method of using cookies worked instead, and to a certain extent it does work, the problem is that this error occurs even with it, and there is even a way to solve this problem by just updating the cookies, but unfortunately it is not a sure thing since depending on how many images you download or how many images you download in a space of time the error happens again, and the problem is that if you are persistent using the cookie method you can have your account suspended, which occurred to me, I can just create another account, but that would make the process of downloading things from twitter a lot more tiring, especially if you have a lot of artists to download things from.

[mikf]

but since yesterday when I went to download images from an artist with a lot of posts it started to give this error

The cached login session probably "expired", but you might be able to still use it by editing your cache file (%APPDATA%\gallery-dl\cache.sqlite3 by default on Windows) with for example DB4S and increasing the expires timestamp value of the gallery_dl.extractor.twitter._login_impl-USERNAME entry.

[Nicosow2]

gallery_dl.extractor.twitter._login_impl-USERNAME

sadly i don't think this gonna work because one of the things that i did trying to fix this error was cleaning my twitter cache (i forgot to mention that in the comment srry), the fact that i don't see this entry anywhere and just gallery_dl.extractor.twitter._guest_token may already say this,

[Nicosow2]

the user and pass method fortunately started working again after a few days (or weeks, I wasn't keeping an eye on it all the time but it wasn't quick) so I'd like to know if there's anything you can do when you come across an account with a lot of posts to avoid this problem again, or is it just luck?

[mikf]

Do not use Twitter's search, only the results from /media/tweets/with_replies. x.com/USER as input URL will use /media + search by default via /timeline, which can be changed with twitter.include.

Searches are the only way to access any Tweets after the first ~1000, but I'm pretty sure Twitter is much more likely to mark your account as suspicious and/or log you out when you are querying the search endpoint a whole lot.

[Nicosow2]

thanks