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.

Sign up for GitHub

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

Jump to bottom

Too Many Requests #11

Open
travisfisher opened this issue Oct 15, 2014 · 2 comments
Open

Too Many Requests #11

travisfisher opened this issue Oct 15, 2014 · 2 comments

Comments

@travisfisher
Copy link

Due to Twitter's API rate limit restrictions on "https://api.twitter.com/1.1/account/verify_credentials.json" (15 per 15 min), it may be beneficial to lookup the user profile using "https://api.twitter.com/1.1/users/show.json" instead (180 per 15 min).

Right now, I'm getting a "Too Many Requests" response from Twitter if I don't cache the data.
@lmammino
Copy link
Member

Hi @tgfisher,
Great suggestion, seem very reasonable. Would you like to submit a pull request?

@logical-and
Copy link

Why don't use application cache for this? Library is not about caching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lmammino @travisfisher @logical-and