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
Specify multiple cookies.txt, and when encountering:
[twitter][info] Waiting until --:--:-- (rate limit)
Switch to next cookies (can be specified in config file.)
It's explicitly account rate limited (not IP), and the artist I want to backup does nude still lifes to practice (very common) so their account isn't able to be downloaded with guest accounts.
Please let me know if this is possible or if there is already a fix.
I want to run multiple instances, but it doesn't fail and give me a cursor to resume from with another account even,
Right now I'm stuck with 3 accounts running these: @artist
@artist/media
from:@artist
and I'm gated by the slowest one, which is heavily rate limited.
Huge Issue when I can only download 300 or so images every 24 hours from an artist with more than 10k image posts.
Specify multiple cookies.txt, and when encountering:
[twitter][info] Waiting until --:--:-- (rate limit)
Switch to next cookies (can be specified in config file.)
It's explicitly account rate limited (not IP), and the artist I want to backup does nude still lifes to practice (very common) so their account isn't able to be downloaded with guest accounts.
Please let me know if this is possible or if there is already a fix.
I want to run multiple instances, but it doesn't fail and give me a cursor to resume from with another account even,
Right now I'm stuck with 3 accounts running these:
@artist
@artist/media
from:@artist
and I'm gated by the slowest one, which is heavily rate limited.
Huge Issue when I can only download 300 or so images every 24 hours from an artist with more than 10k image posts.
I would really like:
[twitter][info] Testing cookies-account-2.txt (rate limit)
...
[twitter][info] Testing cookies-account-3.txt (rate limit)
Let me know if there's a feature I'm missing, but I've had a good look at the documentation and issues relating to this.
The text was updated successfully, but these errors were encountered: