Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

twitter metadata + too many request #526

Closed
wankio opened this issue Dec 20, 2019 · 3 comments
Closed

twitter metadata + too many request #526

wankio opened this issue Dec 20, 2019 · 3 comments

Comments

@wankio
Copy link
Contributor

wankio commented Dec 20, 2019

https://twitter.com/Meiyu_miu/status/1070693241413021696
i dont know why, when i'm using {author[name]} as filename, it named file as Meiyu_miu instead original author CH_DoubleJ

and sometime it have this error 429

[twitter][error] HttpError: '429 Too Many Requests' for 'https://api.twitter.com/1.1/videos/tweet/config/1117243043592060928.json'

@wankio wankio changed the title twitter metadata twitter metadata + too many request Dec 20, 2019
@mikf
Copy link
Owner

mikf commented Dec 20, 2019

This tweet is technically not a retweet, but a quoted tweet (or something like that), and gallery-dl doesn't properly handle them at the moment.

Concerning the 429 error: each user is "only" allowed ~180 requests to fetch video data per 15min and you've managed too exceed that. I'll add some wait time if these errors happen, but you could also manually slow your download speed and frequency with -r and --sleep.

@wankio
Copy link
Contributor Author

wankio commented Dec 21, 2019

so each request sleep 20s ? this is new change from their system ? ty

mikf added a commit that referenced this issue Jan 5, 2020
… and categorize them as retweets
mikf added a commit that referenced this issue Jan 5, 2020
@mikf
Copy link
Owner

mikf commented Jan 5, 2020

Ok, quoted Tweets like https://twitter.com/Meiyu_miu/status/1070693241413021696 are now handled like retweets and filtered accordingly, and rate limit errors (429 Too Many Requests) get dealt with without raising an error.

this is new change from their system

No, the limit was always in place, you usually just didn't reach it and therefore didn't get an error.

@mikf mikf closed this as completed Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants