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

Get Twitter DMs running #39

Open
b3yond opened this issue Sep 25, 2018 · 2 comments
Open

Get Twitter DMs running #39

b3yond opened this issue Sep 25, 2018 · 2 comments
Labels
bug wait for upstream wait to be tested

Comments

@b3yond
Copy link
Member

b3yond commented Sep 25, 2018

Change the Twitter Rate Limit so accounts count the waiting time together with other accounts and not only with itself.
@b3yond b3yond added the bug label Sep 25, 2018
b3yond added a commit that referenced this issue Oct 5, 2018
@b3yond
fixing #39 - saving last request in global var, not db.
304d83f
@b3yond
Copy link
Member Author

b3yond commented Oct 5, 2018

should be fixed, but is not tested yet.

b3yond added a commit that referenced this issue Oct 6, 2018
@b3yond
globals are in a separate python file now #39 #45
5119c6b
@b3yond b3yond added this to the Multi-instance deployment milestone Oct 7, 2018
@b3yond b3yond mentioned this issue Oct 7, 2018
Open
b3yond added a commit that referenced this issue Oct 7, 2018
@b3yond
reverting #39 - make rate limits per account, not app
f59be98
@b3yond b3yond mentioned this issue Oct 7, 2018
Merged
@b3yond
Copy link
Member Author

b3yond commented Oct 11, 2018

Okay, I fixed the problem that twitterDMs.crawl() wasn't called.

Next problem: twitter just changed their API, and tweepy is not updated yet. We have to wait until this gets fixed upstream. the relevant PR is tweepy/tweepy#1109. good luck to them!

@b3yond b3yond changed the title Twitter Rate Limit is app-specific, not account-specific Get Twitter DMs running Oct 11, 2018
b3yond added a commit that referenced this issue Oct 11, 2018
@b3yond
excepted return message 34 so it doesn't get logged #39
4428fa9
@b3yond b3yond mentioned this issue Oct 13, 2018
Merged
@b3yond b3yond removed this from the Multi-instance deployment milestone Jan 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug wait for upstream wait to be tested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@b3yond